On Sat, 13 Jul 2024 at 14:42, Peter Humphrey <peter@prh.myzen.co.uk>wrote:
Hello list,
Where I live, updates to portage itself usually take longer to appear as a binary package than as source, so I can't 'getbinpkg'. Therefore I've set:
# cat /etc/portage/env/nobinpkg.conf
FEATURES="${FEATURES} -getbinpkg"
# cat /etc/portage/package.env
sys-apps/portage nobinpkg.conf
But still portage wants to fetch the binary.
What am I doing wrong?
I don't know what you're doing wrong, but FEATURES is an additive
variable, so adding the ${FEATURES} in there is not necessary.
An alternative might be adding it to emerge default opts in make.conf:
EMERGE_DEFAULT_OPTS="${EMERGE_DEFAULT_OPTS} --usepkg-exclude 'sys-apps/portage'"
On Saturday, 13 July 2024 14:18:09 BST Arve Barsnes wrote:
8
I don't know what you're doing wrong, but FEATURES is an additive
variable, so adding the ${FEATURES} in there is not necessary.
I've tried it without that parenthesis but with no difference.
An alternative might be adding it to emerge default opts in make.conf:
EMERGE_DEFAULT_OPTS="${EMERGE_DEFAULT_OPTS} --usepkg-exclude 'sys-apps/portage'"
Interesting. I hadn't seen that construction before; I'll try it.
Hello list,
Where I live, updates to portage itself usually take longer to appear as a binary package than as source, so I can't 'getbinpkg'. Therefore I've set:
# cat /etc/portage/env/nobinpkg.conf
FEATURES="${FEATURES} -getbinpkg"
# cat /etc/portage/package.env
sys-apps/portage nobinpkg.conf
But still portage wants to fetch the binary.
What am I doing wrong?
It works, but what's wrong with the way I tried it?
Currently, FEATURES=getbinpkg only works as a global setting.
FEATURES are not fully supported in package.env as they can cause
circular effects (e.g. getbinpkg may cause a different version to get selected, which can result in the package.env entry no longer being applicable).
As a matter of curiosity, why do you need to do any such thing at all?
If there is no binary package available for portage yet, then portage
will automatically build it from source instead, which is exactly what setting -getbinpkg for it would do. So why bother?
The only thing that setting -getbinpkg could do is prevent you from
using a binary on the off chance that it happens to appear faster for you.
Note that independent of whether it's useful to exclude this one
package, the functionality doesn't work. You cannot set per-package getbinpkg, this is tracked as https://bugs.gentoo.org/463964
It doesn't do that here. It tries to fetch the binary and bombs out when it can't be found. Then I have to edit make.conf to update Gentoo, then put it back as it was for the rest of the system.
On 14/07/2024 13:04, Peter Humphrey wrote:
It doesn't do that here. It tries to fetch the binary and bombs out when
it can't be found. Then I have to edit make.conf to update Gentoo, then
put it back as it was for the rest of the system.
Do you have PORTAGE_DEFAULT_OPTIONS or whatever it's called set? That's caused me similar grief - it messed up my attempts to update my profile,
it regularly messed up my virtualbox updates, etc etc.
And if you have to edit various environment variables in make.conf, you
know you can override them on the command line?
PORTAGE_DEFAULT_OPTIONS="" emerge virtualbox-modules
as I had to do ...
Yes, I have EMERGE_DEFAULT_OPTS="--jobs=8 --load-average=8 --autounmask=n -- keep-going --nospinner"
Nothing contentious there, I'd have thought.
On Sunday, 14 July 2024 07:05:04 BST Eli Schwartz wrote:
As a matter of curiosity, why do you need to do any such thing at all?
If there is no binary package available for portage yet, then portage
will automatically build it from source instead, which is exactly what
setting -getbinpkg for it would do. So why bother?
It doesn't do that here. It tries to fetch the binary and bombs out when it can't be found. Then I have to edit make.conf to update Gentoo, then put it back as it was for the rest of the system.
Is this about the -1 or --oneshot option?
Where I live, updates to portage itself usually take longer to appear as a binary package than as source, so I can't 'getbinpkg'. Therefore I've set:The main issue is that you aren't syncing portage towards the bin
The main issue is that you aren't syncing portage towards the bin
server, which makes things out of sync and those you will be building a
lot of the packages instead of fetching the binary files when they are
built. One way to come around this issue is that when you sync your
portage, wait a day before you check what files to update, this way the binary packages should have been built, but sure it's a pita.
On Monday, 15 July 2024 10:54:37 BST J. Aho wrote:
The main issue is that you aren't syncing portage towards the bin
server, which makes things out of sync and those you will be building a
lot of the packages instead of fetching the binary files when they are built. One way to come around this issue is that when you sync your portage, wait a day before you check what files to update, this way the binary packages should have been built, but sure it's a pita.
You're right. I had set the sync-uri to mirror.bytemark.co.uk, which I got from the handbook. but I still had GENTOO_MIRRORS="http:// www.mirrorservice.org/sites/distfiles.gentoo.org/" from an older installation.
I've now set the mirror to bytemark; let's see if that helps.
Thanks.
I recall having some trouble with bytemark in the past.
The main issue is that you aren't syncing portage towards the bin
server, which makes things out of sync and those you will be building a
lot of the packages instead of fetching the binary files when they are
built.
If they didn't, then I had the issue as you describe and I had
discussion about this on the gentoo irc channels, but as back then few
people used binhosts so they didn't understand the issue and those
portage don't support to do what you want to do, to filter out new
ebuilds that don't have a binary package at the binhost, just wait
another 20 years and then maybe.
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 491 |
| Nodes: | 16 (2 / 14) |
| Uptime: | 145:55:14 |
| Calls: | 9,694 |
| Calls today: | 4 |
| Files: | 13,731 |
| Messages: | 6,178,580 |