GNU bug report logs -
#41116
Guix deploy fails with new version of Herd
Previous Next
Reported by: alex <at> komputilo.eu
Date: Wed, 6 May 2020 22:24:02 UTC
Severity: important
Done: Ludovic Courtès <ludo <at> gnu.org>
Bug is archived. No further changes may be made.
Full log
Message #30 received at 41116-done <at> debbugs.gnu.org (full text, mbox):
Hi,
Marius Bakke <mbakke <at> fastmail.com> skribis:
> Diego Nicola Barbato <dnbarbato <at> posteo.de> writes:
[...]
>>> I’ve reverted the patch in 5aa4d2dcf2f4f8786358feb45338893ed08a4cd9.
>>>
>>> Diego: I guess we can reinstate the patch “later”, once Shepherd 0.8 can
>>> be considered widespread.
>>
>> I'm sorry I broke reconfigure and deploy. I didn't consider testing
>> upgrading from before Shepherd 0.8 to after my change and I didn't even
>> think of deploy. Going forth I'll leave messing with core functionality
>> to the pros.
>
> Mistakes happen, don't worry about it.
Yup! Plus, the person who reviewed the patch, undoubtedly an equally
nice person, didn’t notice the issue either. :-)
> One thing that would be really useful and can prevent such situations in
> the future is to have a "system test" that tries to run reconfigure from
> the latest released version of Guix (currently 1.1.0).
>
> There are already a few Shepherd tests in gnu/tests/base.scm and
> gnu/tests/reconfigure.scm that can be used as inspiration.
Yes.
I was also wondering if it would make sense for services to somehow
state the major+minor version they’re targeting.
Ludo’.
This bug report was last modified 5 years and 14 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.