all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
To: 36659@debbugs.gnu.org
Subject: bug#36659: There should be an unattended upgrades service
Date: Mon, 15 Jul 2019 12:17:11 +0200	[thread overview]
Message-ID: <20190715101711.gejdpqkyaq2yri3p@pelzflorian.localdomain> (raw)

Some users (want to) forget about regularly upgrading Guix System.
There should be an unattended upgrades service.  Some requirements
come to mind for its configuration:

1) Some users may want their unattended upgrades service to take care
just of reconfiguring from a recent checkout and some may want it to
take care of updating users’ ~/.config/guix/current and ~/guix-profile
profiles.

2) Maybe there should be libnotify integration for unattended
upgrades if the user uses a desktop environment.

3) Updates may fail if there is no internet connection.  Some users
may *not* want upgrades on metered internet connections.  Some users
may *not* want upgrades over untrusted connections.

This report is a followup to Ludo’s proposal at
<https://issues.guix.gnu.org/issue/36636> to add such a service and
add it to %desktop-services, making it the default setting.  Such a
change in defaults could be a bad surprise for some users and should
not go unnoticed, I think.

Regards,
Florian

             reply	other threads:[~2019-07-15 10:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-15 10:17 pelzflorian (Florian Pelz) [this message]
2019-07-16  7:29 ` bug#36659: There should be an unattended upgrades service Matthew Brooks
2019-07-16 12:46   ` Ricardo Wurmus
2019-07-16 13:23     ` Arne Babenhauserheide
2019-07-24 16:35       ` Ludovic Courtès
2019-07-16 14:04   ` pelzflorian (Florian Pelz)
2020-11-30 16:40 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix

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=20190715101711.gejdpqkyaq2yri3p@pelzflorian.localdomain \
    --to=pelzflorian@pelzflorian.de \
    --cc=36659@debbugs.gnu.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.