From: Carlo Zancanaro <carlo@zancanaro.id.au>
To: Pierre Neidhardt <mail@ambrevar.xyz>
Cc: help-guix@gnu.org
Subject: Re: Knowing which services to restart
Date: Wed, 08 Jul 2020 21:08:06 +1000 [thread overview]
Message-ID: <87blkq9sdl.fsf@zancanaro.id.au> (raw)
In-Reply-To: <87eepm1j7w.fsf@ambrevar.xyz>
On Wed, Jul 08 2020, Pierre Neidhardt wrote:
> Couldn't Guix be smarter about this? Or at least provide a less puzzling message.
This was brought up when we originally implemented upgrading of services on a live system. The discussion about this starts in an email from Ludovic[1], and proceeds from there (although you'll have to skip over some other unrelated conversations).
There are definitely ways that things can be improved. I made an attempt at doing this at the end of 2018[2], but that didn't result in anything being merged into Guix. I don't think we've yet settled on an approach for how to resolve this (and the related issue of automatically upgrading services).
Carlo
[1]: https://issues.guix.info/22039#11
[2]: https://issues.guix.info/33508
next prev parent reply other threads:[~2020-07-08 11:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-08 4:56 Knowing which services to restart Matthew Kraai
2020-07-08 8:53 ` Pierre Neidhardt
2020-07-08 11:08 ` Carlo Zancanaro [this message]
2020-07-24 15:28 ` Ludovic Courtès
2020-09-25 13:12 ` Joshua Branson
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87blkq9sdl.fsf@zancanaro.id.au \
--to=carlo@zancanaro.id.au \
--cc=help-guix@gnu.org \
--cc=mail@ambrevar.xyz \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).