Hello,
I've found a bug in shepherd 1.0.1. When a service has a log file in an
'inaccessible' location, e.g. a home service logging to /var/log, it
causes 'herd status $service' to hang, as well as the overall 'herd
service' command. I found it with this service[1] which silently failed
to lo
Hi Dariqq
On Fri, Feb 07 2025, Dariqq wrote:
> I [...] had no issues with logging in.
Actually, neither did I. It is more accurate to write that my
encrypted, FUSE-based home folder did not mount, which resulted in a
shell with the "endpoint disconnected."
> The error comes from the greeter us
Hi Felix,
Felix Lechner writes:
Hi,
On a system updated on or about February 1, I saw this message and could
not log in:
/run/current-system/profiles/etc/profile.d/bash_completion.sh: line
10: shopt: progcomp: invalid shell option name.
Thanks for looking!
Kind regards,
Felix Lechn
Hi,
Dariqq skribis:
>> The situation actually depends on the action you’re running.
>> Starting from 1a8d686b7fa617d9b1df33858957a240b7e11787, shepherd no
>> longer changes directory to the client’s directory. So now it’s up to
>> its action to interpret file names as it wants. We should updat
Correct commit after rebased on master HEAD:
master origin/master 2a4bba2249a71e928bd612d47b6ef439dc498c9c
signature.asc
Description: PGP signature
Hi,
Thank you for reporting this.
I've limited amount of tests to run now it builds successfully:
--8<---cut here---start->8---
> ./pre-inst-env guix build docker-registry
/gnu/store/87a3qjxfnx01vm4yrc6m8sz53mn7ksap-docker-registry-2.8.3
--8<---cut
Previously to this change, the 'guix refresh' download
policy (--key-download)would default to 'interactive', which would throw a
backtrace when guix was invoked with its stdin not connected to a peusdo
terminal (tty). This change makes the new default value 'auto' use
interactive only in an inter
