From: Leo Famulari <leo@famulari.name>
To: Brice Waegeneire <brice@waegenei.re>
Cc: 46194-done@debbugs.gnu.org
Subject: bug#46194: [PATCH] gnu: opendoas: Update to 6.8.1.
Date: Sun, 31 Jan 2021 15:16:06 -0500 [thread overview]
Message-ID: <YBcQBs3WwMdHnzoN@jasmine.lan> (raw)
In-Reply-To: <20210131194107.16894-1-brice@waegenei.re>
On Sun, Jan 31, 2021 at 08:41:07PM +0100, Brice Waegeneire wrote:
> * gnu/packages/admin.scm (opendoas): Update to 6.8.1.
>
> Fixes #46194.
> ---
> As there isn't any service for this package (I'm working on it), it's quite
> useless and there isn't any package depending on it. I guess very few
> people, if any, are using it so I see no need for grafting here.
Thanks! I pushed as 9c8156507abeb15f6d3816800c077fd99f861e3d
The question of "should it be grafted" depends on how many packages
depend on it:
$ guix refresh -l opendoas
No dependents other than itself: opendoas@6.8
If `guix refresh` reports that more than 300 packages will be rebuilt,
security updates should use grafts, as specified in the manual section
Submitting Patches:
https://guix.gnu.org/manual/en/html_node/Submitting-Patches.html
We don't want to wait for a 'staging' or 'core-updates' cycle for
security updates, so grafts let us cheat and push things directly to
master, without requiring expensive recompilation of dependent packages.
I know you could have pushed this yourself, although I did it on your
behalf. Now that we've clarified the use case of grafts, please feel
free to push things like this without review :)
The manual section Commit Access offers some guidelines:
"For patches that just add a new package, and a simple one, it’s OK to
commit, if you’re confident (which means you successfully built it in a
chroot setup, and have done a reasonable copyright and license
auditing). Likewise for package upgrades, except upgrades that trigger a
lot of rebuilds (for example, upgrading GnuTLS or GLib)."
next prev parent reply other threads:[~2021-01-31 20:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-30 20:51 bug#46194: Doas vulnerability CVE-2019-25016 Leo Famulari
2021-01-31 19:41 ` bug#46194: [PATCH] gnu: opendoas: Update to 6.8.1 Brice Waegeneire
2021-01-31 20:16 ` Leo Famulari [this message]
2021-01-31 20:35 ` me--- 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
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=YBcQBs3WwMdHnzoN@jasmine.lan \
--to=leo@famulari.name \
--cc=46194-done@debbugs.gnu.org \
--cc=brice@waegenei.re \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).