On 7/15/24 5:54 AM, 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.
As noted earlier, it's more
On Tuesday, 16 July 2024 09:50:00 BST Michael wrote:
> I recall having some trouble with bytemark in the past.
Now you mention it, so do I, but I've been using it for quite a while now with
no problems.
I suppose servers come and go...
--
Regards,
Peter.
On Monday, 15 July 2024 13:36:19 BST Peter Humphrey wrote:
> 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
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
On 13/07/2024 14.50, Peter Humphrey wrote:
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
server, which makes things out of
Wols Lists wrote:
> On 15/07/2024 07:22, Dale wrote:
>> Is this about the -1 or --oneshot option?
>
> Yes.
>
> Once your system is stable it's a damn good idea :-)
>
> Cheers,
> Wol
>
>
On my recent new rig build, once I installed everything from the world
file from my old system, I added that
On 15/07/2024 07:22, Dale wrote:
Is this about the -1 or --oneshot option?
Yes.
Once your system is stable it's a damn good idea :-)
Cheers,
Wol
Wol wrote:
> On 14/07/2024 14:15, Peter Humphrey wrote:
>> Yes, I have EMERGE_DEFAULT_OPTS="--jobs=8 --load-average=8
>> --autounmask=n --
>> keep-going --nospinner"
>>
>> Nothing contentious there, I'd have thought.
>
> I didn't think I had anything contentious - --once-only and that was
> about
On 7/14/24 8:04 AM, Peter Humphrey wrote:
> 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
On 14/07/2024 14:15, Peter Humphrey wrote:
Yes, I have EMERGE_DEFAULT_OPTS="--jobs=8 --load-average=8 --autounmask=n --
keep-going --nospinner"
Nothing contentious there, I'd have thought.
I didn't think I had anything contentious - --once-only and that was
about it. I think that was
On Sunday, 14 July 2024 13:22:14 BST Wols Lists wrote:
> 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
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
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
Le 14/07/24 à 02:18, Peter Humphrey a tapoté :
> It works, but what's wrong with the way I tried it?
Here is the explanation :
https://bugs.gentoo.org/463964
> Currently, FEATURES=getbinpkg only works as a global setting.
And from :
Eli Schwartz wrote:
> On 7/13/24 8:42 AM, Peter Humphrey 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
>>
On 7/13/24 8:42 AM, Peter Humphrey 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"
>
> #
On Saturday, 13 July 2024 15:49:00 BST Peter Humphrey wrote:
> 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
On Saturday, 13 July 2024 14:18:09 BST Arve Barsnes wrote:
> On Sat, 13 Jul 2024 at 14:42, Peter Humphrey
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:
> >
On Sat, 13 Jul 2024 at 14:42, Peter Humphrey 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}
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
20 matches
Mail list logo
