unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: "Paul A. Patience" <paul@apatience.com>
Cc: 70056@debbugs.gnu.org
Subject: [bug#70056] [RFC PATCH] draft: gnu: Add mfem.
Date: Tue, 02 Apr 2024 17:38:07 +0200	[thread overview]
Message-ID: <87v84z3hcw.fsf@gnu.org> (raw)
In-Reply-To: <adcc00db46287e4467c69bb102a7cb80e088724b.1711634614.git.paul@apatience.com> (Paul A. Patience's message of "Thu, 28 Mar 2024 14:17:39 +0000")

Hi Paul,

"Paul A. Patience" <paul@apatience.com> skribis:

> HEAD is now at 69fbae7 Merge pull request #3841 from mfem/mfem-4.6-dev
> suspicious ownership or permission on `/gnu/store/dc5fx7xfg67fsvl5brdxnbgkirirqxd0-mfem-4.6-checkout'; rejecting this build output
> build of /gnu/store/l0df6d28w16dhnnpcr1qg26xvpmyrkqa-mfem-4.6-checkout.drv failed

Could you try updating guix-daemon?  (You might need to roll back first
to avoid the bug above.)

While fixing
<https://guix.gnu.org/en/blog/2024/fixed-output-derivation-sandbox-bypass-cve-2024-27297/>,
I first pushed a “broken” fix that led to the problem above.  If you
were unlucky and upgraded guix-daemon right at that time (I fixed it
with a followup commit ~24h later), then you have the problem above.

HTH!

Ludo’.




  parent reply	other threads:[~2024-04-02 15:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-28 14:17 [bug#70056] [RFC PATCH] draft: gnu: Add mfem Paul A. Patience
2024-03-29  4:40 ` [bug#70056] [RFC PATCH v2] " Paul A. Patience
2024-04-02 15:38 ` Ludovic Courtès [this message]
2024-04-02 17:41 ` [bug#70056] [PATCH] " Paul A. Patience

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=87v84z3hcw.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=70056@debbugs.gnu.org \
    --cc=paul@apatience.com \
    /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).