unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Maxime Devos <maximedevos@telenet.be>
Cc: 54485@debbugs.gnu.org
Subject: [bug#54485] [PATCH] gnu: Add guile-with-openat.
Date: Thu, 24 Mar 2022 12:37:36 +0100	[thread overview]
Message-ID: <87czibd1j3.fsf@gnu.org> (raw)
In-Reply-To: <20220320215031.306710-1-maximedevos@telenet.be> (Maxime Devos's message of "Sun, 20 Mar 2022 21:50:31 +0000")

Hi,

Maxime Devos <maximedevos@telenet.be> skribis:

> XXX Don't apply yet, let's wait for
> "./pre-inst-env guix build guile-with-openat" to complete first.
>
> This will allow us to work on resolving the >1 year publicly
> known privilege escalation, see <https://issues.guix.gnu.org/47584>.
>
> * gnu/packages/guile.scm (guile-with-openat): New variable.

It’s a clever way to remind me (and other interested Guile committers)
of how late we are when it comes to patch review.

I’d rather avoid carrying this many patches in a package, be it Guile or
anything else; that’s not something we usually do.

Instead, I would prefer to actually review and apply the patches
upstream.  I’ve been meaning to do that, really, but it requires a chunk
of time and focus, which keeps leading me to postpone.

Is the latest patch set on guile-devel?  It’s not mentioned at
<https://issues.guix.gnu.org/46258>.

Thanks,
Ludo’.




  parent reply	other threads:[~2022-03-24 11:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-20 21:50 [bug#54485] [PATCH] gnu: Add guile-with-openat Maxime Devos
2022-03-20 22:39 ` Maxime Devos
2022-03-21 14:24   ` Maxime Devos
2022-03-24 11:37 ` Ludovic Courtès [this message]
2022-03-24 11:55   ` Maxime Devos
2022-06-13  0:31 ` Tobias Geerinckx-Rice via Guix-patches via
2023-02-24 22:57 ` Ludovic Courtès

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=87czibd1j3.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=54485@debbugs.gnu.org \
    --cc=maximedevos@telenet.be \
    /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).