From: Leo Famulari <leo@famulari.name>
To: Gottfried <gottfried@posteo.de>
Cc: help-guix@gnu.org
Subject: Re: guix pull
Date: Wed, 16 Feb 2022 15:27:40 -0500 [thread overview]
Message-ID: <Yg1ePGqCgR5IX4pK@jasmine.lan> (raw)
In-Reply-To: <2b539a93-d9e8-a561-2bf4-15b62717965a@posteo.de>
On Wed, Feb 16, 2022 at 07:28:35PM +0000, Gottfried wrote:
> In other Linux distros there is always an immediate announcement if there
> are security updates and package updates available.
>
> In guix system it seems, according to Your answer, it does not happen.
> (May be in future if it will be developed?)
Overall, it's a complicated subject.
Different distros handle security updates in different ways. Some of
them are better than Guix, some are worse. And whether or not you think
they are better or worse depends on your preferences.
There is not a simple answer to "what is the right thing to do?" in
terms of security updates and advisories.
Guix is a distro run by volunteers, and nobody has volunteered to handle
advisories, nor has anybody offered to fund that work. So, it hasn't
happened yet.
next prev parent reply other threads:[~2022-02-16 20:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-16 16:28 guix pull Gottfried
2022-02-16 17:19 ` Leo Famulari
2022-02-16 17:55 ` pelzflorian (Florian Pelz)
2022-02-16 19:22 ` Gottfried
2022-02-16 19:28 ` Gottfried
2022-02-16 20:27 ` Leo Famulari [this message]
2022-02-16 20:09 ` Ricardo Wurmus
2022-02-16 20:35 ` Gottfried
2022-02-16 22:36 ` Ricardo Wurmus
2022-02-16 20:38 ` Gottfried
2022-02-16 22:58 ` Ricardo Wurmus
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=Yg1ePGqCgR5IX4pK@jasmine.lan \
--to=leo@famulari.name \
--cc=gottfried@posteo.de \
--cc=help-guix@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.
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).