> > i stopped rebasing my shepherd commits. abandoning them does feel like
> > an enormous waste, but i'm cutting my losses at this point.
>
>
> You were probably right to do so.
>
> From what I remember, Ludo' did not like debugging statements all over
> the place. There was a disconnect that prev
Hi Attila,
On Mon, Sep 16 2024, Attila Lendvai wrote:
> i stopped rebasing my shepherd commits. abandoning them does feel like
> an enormous waste, but i'm cutting my losses at this point.
You were probably right to do so.
>From what I remember, Ludo' did not like debugging statements all over
> Okay, then there is still another problem. I am unable to reconfigure
> my systems via 'guix deploy' when a timer is enabled already. I am
> trying to add a second timer.
sadly, i cannot test your reproducer without substantial work.
my patches that clean up error handling in shepherd are from
Hi Attila,
On Tue, Jul 02 2024, Attila Lendvai wrote:
> i forgot to add that it's fixed
Okay, then there is still another problem. I am unable to reconfigure
my systems via 'guix deploy' when a timer is enabled already. I am
trying to add a second timer.
The command stalls with messages like
> (un?)fortunately, i can't reproduce it on a recent guix and shepherd.
i forgot to add that it's fixed by a guix commit:
services: shepherd: Failure to load a service does not prevent booting.
https://git.savannah.gnu.org/cgit/guix.git/commit/?id=cca25a67693bb68a1884a081b415a43fad1e8641
--
• a
> > I still don't know how to fix the issue properly, but at least I can
> > reconfigure my system now <3
>
>
> I have a reproducer! In the code below, please change "sunday" to "0",
> together with this line in your "services":
(un?)fortunately, i can't reproduce it on a recent guix and shephe
On Fri, Jun 28 2024, Felix Lechner wrote:
> even the Magic SysRq key 'i' [...] enough will not stop it.
Sorry, I meant to write 'e' which presumably refers to SIGTERM rather
than SIGKILL.
