Hi,
Mathieu Othacehe skribis:
> Thanks for the fix! The jami and jami-provisioning tests are also broken
> because of what looks like to be the same issue:
>
> One does not simply initialize the client: Another daemon is detected
> /gnu/store/01phrvxnxrg1q0gxa35g7f77q06crf6v-shepherd-marionette.
Hi,
Mathieu Othacehe skribis:
> I think however that it would be nice to create a wip branch for those
> changes, deploy it and monitor it closely on Berlin before pushing. From
> experience, the publish code is really fragile and the I/O pressure on
> Berlin can exhibit a lot of unexpected issu
Hello,
The ldap test in intermittently failing:
https://ci.guix.gnu.org/build/703858/log/raw.
It looks like the ldap_bind call is failing:
ldap_bind: Invalid credentials (49)
and the "eva" user is hence not created. Ricardo any idea what could be
going wrong?
Here is the log of a successful r
On 13/1/22 08:22, Simon South wrote:
No, this would've been a volume I created myself; I expect only users
who are partitioning their drives manually or replacing an existing
system would encounter this.
+1. I encountered this while installing Guix on my pre-existing LUKS
volume that I share w
