From: Robert Vollmert <rob@vllmrt.net>
To: "Jakob L. Kreuze" <zerodaysfordays@sdf.lonestar.org>
Cc: guix-devel@gnu.org, 36878@debbugs.gnu.org
Subject: bug#36878: guix system reconfigure broken
Date: Thu, 1 Aug 2019 10:30:27 +0200 [thread overview]
Message-ID: <AF85F3A1-9899-4F5C-AE81-42A52DE71386__39271.2910122768$1564648274$gmane$org@vllmrt.net> (raw)
In-Reply-To: <87k1bycbn8.fsf@sdf.lonestar.org>
> On 31. Jul 2019, at 20:16, Jakob L. Kreuze <zerodaysfordays@sdf.lonestar.org> wrote:
>
> Hi Robert,
>
> Robert Vollmert <rob@vllmrt.net> 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 A
>>
>> After reverting this commit, if I perform these steps, I end up with
>> nginx running with config file B in 5.
>
> Okay, I see now. Thank you clarifying. Would you be willing to see if
> the patch provided by #36880 fixes this issue?
Yes, it seems it does!
next prev parent reply other threads:[~2019-08-01 8:31 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-31 16:18 bug#36878: guix system reconfigure broken Robert Vollmert
2019-07-31 16:45 ` Jakob L. Kreuze
2019-07-31 16:45 ` Jakob L. Kreuze
2019-07-31 17:06 ` Robert Vollmert
2019-07-31 18:16 ` Jakob L. Kreuze
2019-08-01 8:30 ` Robert Vollmert [this message]
2019-08-01 8:30 ` Robert Vollmert
2019-08-01 14:10 ` Jakob L. Kreuze
2019-08-02 15:11 ` Jakob L. Kreuze
2019-08-05 10:07 ` ison
2019-08-05 11:47 ` Ricardo Wurmus
2019-08-05 14:59 ` Jakob L. Kreuze
2019-08-06 2:55 ` ison
2019-08-06 2:55 ` ison
2019-08-05 11:47 ` Ricardo Wurmus
2019-08-23 12:55 ` Ludovic Courtès
2019-08-02 15:11 ` Jakob L. Kreuze
2019-08-01 14:10 ` Jakob L. Kreuze
2019-07-31 18:16 ` Jakob L. Kreuze
2019-07-31 17:06 ` Robert Vollmert
2019-08-01 9:21 ` Alex Sassmannshausen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='AF85F3A1-9899-4F5C-AE81-42A52DE71386__39271.2910122768$1564648274$gmane$org@vllmrt.net' \
--to=rob@vllmrt.net \
--cc=36878@debbugs.gnu.org \
--cc=guix-devel@gnu.org \
--cc=zerodaysfordays@sdf.lonestar.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.