From: Arne Babenhauserheide <arne_bab@web.de>
To: 36659@debbugs.gnu.org
Subject: bug#36659: There should be an unattended upgrades service
Date: Tue, 16 Jul 2019 15:23:35 +0200 [thread overview]
Message-ID: <87wogiglk8.fsf@web.de> (raw)
In-Reply-To: <87sgr6gn9h.fsf@elephly.net>
[-- Attachment #1: Type: text/plain, Size: 1274 bytes --]
Ricardo Wurmus <rekado@elephly.net> writes:
>> Further, an automatic upgrade service wouldn't really add anything
>> useful, since cron jobs and scripts can already be used to automate
>> upgrading if one so desires.
>
> I disagree. We provide a whole lot of services that aren’t strictly
> necessary in order to satisfy what we think are reasonable user
> expectations. An upgrade service that’s easily removed or configured
> seems nicer to me than having to muck about with cron jobs and scripts
> by myself.
I would most of all like to see a CVE-checking service that tells me
about security updates. Sometimes I’ll ignore updates for a few weeks
because I have a setup that absolutely must keep working, because I
could not even afford half an hour of brokenness, but I must still do
security updates, and I would like Guix to tell me about those.
Also it would be interesting to have an auto-update service that only
updates /run/current-system
That way users would only have to worry about their personal
installations, but not about the underlying base-system. I think there
are many users who would be most happy if they never had to sudo.
Best wishes,
Arne
--
Unpolitisch sein
heißt politisch sein
ohne es zu merken
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 1076 bytes --]
next prev parent reply other threads:[~2019-07-16 13:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-15 10:17 bug#36659: There should be an unattended upgrades service pelzflorian (Florian Pelz)
2019-07-16 7:29 ` Matthew Brooks
2019-07-16 12:46 ` Ricardo Wurmus
2019-07-16 13:23 ` Arne Babenhauserheide [this message]
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=87wogiglk8.fsf@web.de \
--to=arne_bab@web.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.