Michael wrote:
> On Sunday, 7 April 2024 20:17:31 BST Dale wrote:
>> Howdy,
>>
>> A while back using overlays changed. Using eselect is supposed to be
>> the new way, and easier. Either I'm missing something or something is
>> missing from the docs. I tried to add voyageur to my NAS box/backup
On Sunday, 7 April 2024 20:17:31 BST Dale wrote:
> Howdy,
>
> A while back using overlays changed. Using eselect is supposed to be
> the new way, and easier. Either I'm missing something or something is
> missing from the docs. I tried to add voyageur to my NAS box/backup
> rig. The command
On 4/6/24 18:38, Andrew Udvare wrote:
On Sat, 6 Apr 2024 at 21:32, Daniel Frey wrote:
What's even stranger is if I manually start it and restart lircd it works!
Have you tried adding Before=lircd.service in the [Unit] section?
OK, I have finally sorted out the IR keymap/lircd/irexec/LCDd
Howdy,
A while back using overlays changed. Using eselect is supposed to be
the new way, and easier. Either I'm missing something or something is
missing from the docs. I tried to add voyageur to my NAS box/backup
rig. The command to add it works fine. However, when I try to sync it,
either
On 07/04/2024 16:08, Michael wrote:
Cool, once your system is up to date you should be able to change your profile
and follow the rest of the instructions. I hope all goes well.
emerge --emptytree is now running well - 122 of 1534 so it has some way
to go ...
Cheers,
Wol
On 4/6/24 18:38, Andrew Udvare wrote:
On Sat, 6 Apr 2024 at 21:32, Daniel Frey wrote:
What's even stranger is if I manually start it and restart lircd it works!
Have you tried adding Before=lircd.service in the [Unit] section?
I did, it made no difference.
From what I can tell it is
On 07/04/2024 15:46, Wols Lists wrote:
On 07/04/2024 13:07, Michael wrote:
On Sunday, 7 April 2024 12:04:32 BST Wols Lists wrote:
On 07/04/2024 11:48, Wols Lists wrote:
On 07/04/2024 11:23, Michael wrote:
On Sunday, 7 April 2024 11:21:00 BST Wols Lists wrote:
On 07/04/2024 11:00, Wols Lists
On Sunday, 7 April 2024 15:46:18 BST Wols Lists wrote:
> On 07/04/2024 13:07, Michael wrote:
> > Did you emerge any packages using the new 23.0 profile, then went back to
> > the old profile to run the above command?
>
> No ...
>
> Ummm ... I have had trouble emerging other stuff that didn't
On 07/04/2024 13:07, Michael wrote:
On Sunday, 7 April 2024 12:04:32 BST Wols Lists wrote:
On 07/04/2024 11:48, Wols Lists wrote:
On 07/04/2024 11:23, Michael wrote:
On Sunday, 7 April 2024 11:21:00 BST Wols Lists wrote:
On 07/04/2024 11:00, Wols Lists wrote:
What do I do here - "emerge
On Sunday, 7 April 2024 12:04:32 BST Wols Lists wrote:
> On 07/04/2024 11:48, Wols Lists wrote:
> > On 07/04/2024 11:23, Michael wrote:
> >> On Sunday, 7 April 2024 11:21:00 BST Wols Lists wrote:
> >>> On 07/04/2024 11:00, Wols Lists wrote:
> What do I do here - "emerge binutils" (step 9)
On 07/04/2024 11:48, Wols Lists wrote:
On 07/04/2024 11:23, Michael wrote:
On Sunday, 7 April 2024 11:21:00 BST Wols Lists wrote:
On 07/04/2024 11:00, Wols Lists wrote:
What do I do here - "emerge binutils" (step 9) wants to emerge gcc,
which the instructions say "emerge AFTER binutils".
On Sunday, 7 April 2024 11:48:07 BST Wols Lists wrote:
> On 07/04/2024 11:23, Michael wrote:
> > On Sunday, 7 April 2024 11:21:00 BST Wols Lists wrote:
> >> On 07/04/2024 11:00, Wols Lists wrote:
> >>> What do I do here - "emerge binutils" (step 9) wants to emerge gcc,
> >>> which the instructions
On Friday, 5 April 2024 16:21:15 BST Michael Orlitzky wrote:
> But barring that, you could add pre- and post-stop hooks that will let you
> know that the daemon is stopping.
>
> For example, in /etc/conf.d/boinc, you could put
>
> stop_pre(){
> touch /run/stopping-boinc
> }
>
On 07/04/2024 11:23, Michael wrote:
On Sunday, 7 April 2024 11:21:00 BST Wols Lists wrote:
On 07/04/2024 11:00, Wols Lists wrote:
What do I do here - "emerge binutils" (step 9) wants to emerge gcc,
which the instructions say "emerge AFTER binutils".
With gcc it says "don't let it emerge
On 07/04/2024 11:15, Michael wrote:
On Sunday, 7 April 2024 11:00:49 BST Wols Lists wrote:
What do I do here - "emerge binutils" (step 9) wants to emerge gcc,
which the instructions say "emerge AFTER binutils".
With gcc it says "don't let it emerge glibc", should I apply the same
logic and not
On 07/04/2024 11:15, Michael wrote:
On Sunday, 7 April 2024 11:00:49 BST Wols Lists wrote:
What do I do here - "emerge binutils" (step 9) wants to emerge gcc,
which the instructions say "emerge AFTER binutils".
With gcc it says "don't let it emerge glibc", should I apply the same
logic and not
On Sunday, 7 April 2024 11:21:00 BST Wols Lists wrote:
> On 07/04/2024 11:00, Wols Lists wrote:
> > What do I do here - "emerge binutils" (step 9) wants to emerge gcc,
> > which the instructions say "emerge AFTER binutils".
> >
> > With gcc it says "don't let it emerge glibc", should I apply the
On 07/04/2024 11:00, Wols Lists wrote:
What do I do here - "emerge binutils" (step 9) wants to emerge gcc,
which the instructions say "emerge AFTER binutils".
With gcc it says "don't let it emerge glibc", should I apply the same
logic and not let binutils emerge gcc?
Just to follow up to
On Sunday, 7 April 2024 11:00:49 BST Wols Lists wrote:
> What do I do here - "emerge binutils" (step 9) wants to emerge gcc,
> which the instructions say "emerge AFTER binutils".
>
> With gcc it says "don't let it emerge glibc", should I apply the same
> logic and not let binutils emerge gcc?
>
What do I do here - "emerge binutils" (step 9) wants to emerge gcc,
which the instructions say "emerge AFTER binutils".
With gcc it says "don't let it emerge glibc", should I apply the same
logic and not let binutils emerge gcc?
Cheers,
Wol
20 matches
Mail list logo
