From: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
To: Maxime Devos <maximedevos@telenet.be>
Cc: 54651@debbugs.gnu.org
Subject: bug#54651: Guix pull failing on ARM 32bit with "Please report the COMPLETE output above by email"
Date: Tue, 24 May 2022 00:18:57 +0200 [thread overview]
Message-ID: <20220524001857.25343d6d@primarylaptop.localdomain> (raw)
In-Reply-To: <20220523210820.72ebe849@primarylaptop.localdomain>
[-- Attachment #1: Type: text/plain, Size: 671 bytes --]
On Mon, 23 May 2022 21:08:20 +0200
Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org> wrote:
> I'll now try with the current HEAD to see if that's somehow fixed.
I've a similar failure with HEAD:
> \ 'check' phasebuilder for `/gnu/store/m1iyn6y1s3ajl6v0lv5658zq2cngdpq3-ruby-stackprof-0.2.17.drv' failed with exit code 1
> build of /gnu/store/m1iyn6y1s3ajl6v0lv5658zq2cngdpq3-ruby-stackprof-0.2.17.drv failed
> View build log at '/var/log/guix/drvs/m1/iyn6y1s3ajl6v0lv5658zq2cngdpq3-ruby-stackprof-0.2.17.drv.bz2'.
> cannot build derivation
> `/gnu/store/i6zxh4qblndfaqgz62fcm2s983pqj3ak-ruby-rubocop-1.10.0.drv':
> 1 dependencies couldn't be built
Denis.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-05-23 22:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-31 12:15 bug#54651: Guix pull failing on ARM 32bit with "Please report the COMPLETE output above by email" Denis 'GNUtoo' Carikli
2022-04-05 15:02 ` Denis 'GNUtoo' Carikli
2022-05-18 13:47 ` Denis 'GNUtoo' Carikli
2022-05-23 13:40 ` Denis 'GNUtoo' Carikli
2022-05-23 14:10 ` Maxime Devos
2022-05-23 14:22 ` raingloom
2022-05-23 17:30 ` Denis 'GNUtoo' Carikli
2022-05-23 18:27 ` Maxime Devos
2022-05-23 19:08 ` Denis 'GNUtoo' Carikli
2022-05-23 22:18 ` Denis 'GNUtoo' Carikli [this message]
2022-05-24 8:34 ` Maxime Devos
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=20220524001857.25343d6d@primarylaptop.localdomain \
--to=gnutoo@cyberdimension.org \
--cc=54651@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 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.