Hello,
zerodaysford...@sdf.lonestar.org (Jakob L. Kreuze) skribis:
> zerodaysford...@sdf.lonestar.org (Jakob L. Kreuze) writes:
>
>> Great :)
>>
>> CC'ing Chris and Dave since I don't have write access -- can we
>> fast-track #36880 into master? I'd consider this to be a high-priority
>> bug
On Mon, Aug 05, 2019 at 10:59:57AM -0400, Jakob L. Kreuze wrote:
> ison -- I'm very sorry that you've had this experience. Would you be
> willing to share the 'bootloader' field of your operating system
> configuration so I can look into this?
Thanks for taking an interest. Here is the new bug
Hi ison and Ricardo,
Ricardo Wurmus writes:
> ison writes:
>
>> I made the mistake of rebooting my machine after I first got this
>> error, I thought perhaps it was benign. But when it came back up I
>> was dropped to a GRUB rescue shell with some error about
>> "grub_file_filters" being an
ison writes:
> I made the mistake of rebooting my machine after I first got this error, I
> thought perhaps it was benign. But when it came back up I was dropped to a
> GRUB rescue shell with some error about "grub_file_filters" being an unknown
> symbol.
This eems unrelated. The problem
On Fri, Aug 02, 2019 at 11:11:31AM -0400, Jakob L. Kreuze wrote:
> The patch made it into master as 1db6f137d; thanks to Danny for signing
> off on it. Should we close this?
I'm still experiencing this issue. "guix describe" shows that I'm using
commit 35600cd which should be newer than the fix.
zerodaysford...@sdf.lonestar.org (Jakob L. Kreuze) writes:
> Great :)
>
> CC'ing Chris and Dave since I don't have write access -- can we
> fast-track #36880 into master? I'd consider this to be a high-priority
> bug fix.
>
> Regards,
> Jakob
The patch made it into master as 1db6f137d; thanks to
Robert Vollmert writes:
> Yes, it seems it does!
Great :)
CC'ing Chris and Dave since I don't have write access -- can we
fast-track #36880 into master? I'd consider this to be a high-priority
bug fix.
Regards,
Jakob
signature.asc
Description: PGP signature
Thanks for reporting this, I experienced the same issue but blamed it on
my own infrastructure instead!
Good to hear it's resolved now.
Alex
Robert Vollmert writes:
> Hi,
>
> it appears that commit 5c8c8c455420af27189d6045b3599fe6e27ad012
>
> guix system: Reimplement 'reconfigure’.
>
>
> On 31. Jul 2019, at 20:16, Jakob L. Kreuze
> wrote:
>
> Hi Robert,
>
> Robert Vollmert writes:
>
>> The concrete problem is this:
>>
>> 1. nginx is running with config file A
>> 2. make some change to nginx config
>> 3. run guix system reconfigure (which builds a new nginx config file
Hi Robert,
Robert Vollmert writes:
> The concrete problem is this:
>
> 1. nginx is running with config file A
> 2. make some change to nginx config
> 3. run guix system reconfigure (which builds a new nginx config file B)
> 4. run herd restart nginx
> 5. nginx is still running with config file
> On 31. Jul 2019, at 18:45, Jakob L. Kreuze
> wrote:
> Robert Vollmert writes:
>
>> Hi,
>>
>> it appears that commit 5c8c8c455420af27189d6045b3599fe6e27ad012
>>
>> guix system: Reimplement 'reconfigure’.
>>
>> breaks guix system reconfigure. In particular, after reconfiguring,
>>
Hi Robert,
Robert Vollmert writes:
> Hi,
>
> it appears that commit 5c8c8c455420af27189d6045b3599fe6e27ad012
>
> guix system: Reimplement 'reconfigure’.
>
> breaks guix system reconfigure. In particular, after reconfiguring,
> shepherd doesn’t know about the updated versions of services.
>
>
12 matches
Mail list logo
