From: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
To: Michael Ford <fanquake@gmail.com>
Cc: 69755@debbugs.gnu.org
Subject: bug#69755: Issue trying to guix pull
Date: Tue, 12 Mar 2024 20:23:20 +0100 [thread overview]
Message-ID: <87a5n3tftj.fsf@pelzflorian.de> (raw)
In-Reply-To: <CAFyhPjVi7NZdeeeNYRz-NSaCKa704We6c-y21Hz7F5DWuqs4hQ@mail.gmail.com> (Michael Ford's message of "Tue, 12 Mar 2024 16:55:58 +0000")
Hello Michael.
Michael Ford <fanquake@gmail.com> writes:
> building /gnu/store/p9nimij8lz4yln5jd3gm0kdhirrwz56h-guix-1.4.0-18.4c94b9e-checkout.drv...
> -suspicious ownership or permission on
> `/gnu/store/bj2rp8ql9zxnv4l9gvlhph55fa241mk4-guix-1.4.0-18.4c94b9e-checkout';
> rejecting this build output
> Backtrace:
A probable fix was pushed by Ludovic recently.
Does it work? Can this issue be closed?
commit ff1251de0bc327ec478fc66a562430fbf35aef42
Author: Ludovic Courtès <ludo@gnu.org>
Date: Tue Mar 12 11:53:35 2024 +0100
daemon: Address shortcoming in previous security fix for CVE-2024-27297.
This is a followup to 8f4ffb3fae133bb21d7991e97c2f19a7108b1143.
Commit 8f4ffb3fae133bb21d7991e97c2f19a7108b1143 fell short in two
ways: (1) it didn’t have any effet for fixed-output derivations
performed in a chroot, which is the case for all of them except those
using “builtin:download” and “builtin:git-download”, and (2) it did not
preserve ownership when copying, leading to “suspicious ownership or
permission […] rejecting this build output” errors.
Regards,
Florian
next prev parent reply other threads:[~2024-03-12 19:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-12 16:55 bug#69755: Issue trying to guix pull Michael Ford
2024-03-12 19:23 ` pelzflorian (Florian Pelz) [this message]
2024-03-12 19:33 ` Michael Ford
2024-03-12 19:33 ` pelzflorian (Florian Pelz)
2024-03-13 10:11 ` Michael Ford
2024-03-13 11:24 ` pelzflorian (Florian Pelz)
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=87a5n3tftj.fsf@pelzflorian.de \
--to=pelzflorian@pelzflorian.de \
--cc=69755@debbugs.gnu.org \
--cc=fanquake@gmail.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).