all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Josselin Poiret via Bug reports for GNU Guix <bug-guix@gnu.org>
To: "André A. Gomes" <andre@atlas.engineer>, 63394@debbugs.gnu.org
Subject: bug#63394: guix pack and proot
Date: Wed, 31 May 2023 19:20:04 +0200	[thread overview]
Message-ID: <87h6rsquyj.fsf@jpoiret.xyz> (raw)
In-Reply-To: <87ttvvi8zo.fsf@atlas.engineer>

[-- Attachment #1: Type: text/plain, Size: 870 bytes --]

Hi André,

André A. Gomes <andre@atlas.engineer> writes:

> Hi Guix,
>
> I acknowledge the answers provided, but I'd like to emphasize that guix
> pack won't run if proot is broken.  This is a critical issue and a
> temporary solution is simple enough: disable the tests for the current
> proot version packaged.

As I mentioned above, disabling the tests is not a solution here, since
one of the tests failing is *actually* indicative of a regression in
PRoot, and we should not ignore it.  Specifically, it seems the
interaction between pthreads and current working directory sandboxing
isn't working IIRC.  I haven't heard back from upstream, I might have a
look at some point but I have no familiarity whatsoever with its
codebase (and I guess it's using some nasty tricks that will take some
time to understand).

Best,
-- 
Josselin Poiret

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 682 bytes --]

      reply	other threads:[~2023-05-31 17:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-09 18:05 bug#63394: Unable to build proot-static locally André A. Gomes
2023-05-09 18:36 ` bug#63394: (no subject) André A. Gomes
2023-05-09 18:43   ` Josselin Poiret via Bug reports for GNU Guix
2023-05-29 13:04 ` bug#63394: guix pack and proot André A. Gomes
2023-05-31 17:20   ` Josselin Poiret via Bug reports for GNU Guix [this message]

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87h6rsquyj.fsf@jpoiret.xyz \
    --to=bug-guix@gnu.org \
    --cc=63394@debbugs.gnu.org \
    --cc=andre@atlas.engineer \
    --cc=dev@jpoiret.xyz \
    /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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.