Hi again,
[...]
> Perhaps services should allow specifying the minimum required Shepherd
> version, which Shepherd could ensure is met before attempting to restart
> a service, printing something like:
>
> 'Could not restart service X due to unmet Shepherd version requirement;
> the service will
retitle 55898 Services depending on new Shepherd features may fail until
a reboot
thanks
Hi,
Maxim Cournoyer writes:
[...]
> I'm suspecting that given the service makes use of Shepherd 0.9
> features, perhaps it fails loading and the error is reported erroneously
> that way... a reboot would t
retitle 55898 jami service fails to start following reconfigure
thanks
Hello,
Maxim Cournoyer writes:
> Hello Maxime,
>
> Maxime Devos writes:
>
>> Maxim Cournoyer schreef op za 11-06-2022 om 01:53 [-0400]:
>>> I don't get it; how can the service runs fine in the instrumented VMs
>>> the syste
Hello Maxime,
Maxime Devos writes:
> Maxim Cournoyer schreef op za 11-06-2022 om 01:53 [-0400]:
>> I don't get it; how can the service runs fine in the instrumented VMs
>> the system tests use, and fail in my updated machine? Could it be a
>> fault in 'guix deploy'?
>
> Maybe the shepherd has t
Maxim Cournoyer schreef op za 11-06-2022 om 01:53 [-0400]:
> I don't get it; how can the service runs fine in the instrumented VMs
> the system tests use, and fail in my updated machine? Could it be a
> fault in 'guix deploy'?
Maybe the shepherd has the old (gnu build jami-service) module loaded
Hello Guix!
After having fixed the tests of the jami-service-type and pushed the fix
as 85b4dabd94d53f8179f31a42046cd83fc3a352fc, I was confident it would
work, but my freshly 'guix deploy'ed machine says otherwise:
--8<---cut here---start->8---
$ sudo herd sto
