From: Ivan Vilata i Balaguer <ivan@selidor.net>
To: Blake Shaw <blake@reproduciblemedia.com>
Cc: Josselin Poiret <dev@jpoiret.xyz>,
63284@debbugs.gnu.org, Ivan Vilata i Balaguer <ivan@selidor.net>
Subject: bug#63284: proot: Build gets stuck in test-0cf405b0 (and maybe test-25069c13)
Date: Fri, 19 May 2023 14:36:31 +0200 [thread overview]
Message-ID: <ZGdtT+kzA3kthgSz@sax> (raw)
In-Reply-To: <7zmt2gfrfh.fsf@reproduciblemedia.com>
[-- Attachment #1: Type: text/plain, Size: 1052 bytes --]
Same for me both building with:
guix build proot --with-version=proot=5.4.0
And altering the definition of the package manually to use `(version "5.4.0")`
(hash `186qsg4yvisqjgf8w5jxhnlig7x341vpqwcgp8as3r59qmqkpmk7`), plus removing
`libarchive` from `inputs` (as v5.3.1 already removed that dependency).
Thanks!
Blake Shaw (2023-05-07 15:55:04 +0700) wrote:
> I'm also dealing with the issue, except for me it gets stuck in
> test-kkkkkkk, if that info is helpful at all.
>
> Josselin Poiret via Bug reports for GNU Guix <bug-guix@gnu.org> writes:
>
> > Ivan Vilata i Balaguer <ivan@selidor.net> writes:
> >
> >> Hi! It looks like some tests during the build of `proot` get stuck in the
> >> version of Guix shown below:
> >
> > I already provided fixes for two tests upstream [1] but I'm waiting on
> > [2] since it seems like an actual regression.
>
> > [1] https://github.com/proot-me/proot/pull/351
> > [2] https://github.com/proot-me/proot/issues/352
--
Ivan Vilata i Balaguer -- https://elvil.net/
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2023-05-19 12:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-04 21:52 bug#63284: proot: Build gets stuck in test-0cf405b0 (and maybe test-25069c13) Ivan Vilata i Balaguer
2023-05-05 9:31 ` Josselin Poiret via Bug reports for GNU Guix
2023-05-07 8:55 ` Blake Shaw via Bug reports for GNU Guix
2023-05-19 12:36 ` Ivan Vilata i Balaguer [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=ZGdtT+kzA3kthgSz@sax \
--to=ivan@selidor.net \
--cc=63284@debbugs.gnu.org \
--cc=blake@reproduciblemedia.com \
--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.