From: xdrcft56 via Bug reports for GNU Guix <bug-guix@gnu.org>
To: Maxime Devos <maximedevos@telenet.be>
Cc: 53511@debbugs.gnu.org
Subject: bug#53511: guix pull command fails
Date: Mon, 24 Jan 2022 23:35:02 +0000 [thread overview]
Message-ID: <HUlrLGynICEibzthGimGKkW6pAdXH50Ywc_PIpNrFjNayqEvcjYNmTLxpU_dgVYmlzHKZESPV6WszqT2wcrwHl0pDgVTAs72_aeoK0TX384=@protonmail.com> (raw)
In-Reply-To: <35df500da3867665aadb4fadef73e649d5aec30e.camel@telenet.be>
[-- Attachment #1: Type: text/plain, Size: 981 bytes --]
Thank you. I've attached the requested log file (/var/log/guix/drvs/aj/mmafhpmi83ssxg860wd93z9yhhhk5w-gcc-10.3.0.drv.bz2).
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Monday, January 24th, 2022 at 4:25 PM, Maxime Devos <maximedevos@telenet.be> wrote:
> xdrcft56 via Bug reports for GNU Guix schreef op ma 24-01-2022 om 18:28
>
> [+0000]:
>
> > / 'build' phasebuilder for
> >
> > `/gnu/store/ajmmafhpmi83ssxg860wd93z9yhhhk5w-gcc-10.3.0.drv' failed
> >
> > with exit code 1
> >
> > build of /gnu/store/ajmmafhpmi83ssxg860wd93z9yhhhk5w-gcc-10.3.0.drv
> >
> > failed
> >
> > Backtrace:
> >
> > View build log at
> >
> > '/var/log/guix/drvs/aj/mmafhpmi83ssxg860wd93z9yhhhk5w-gcc-
> >
> > 10.3.0.drv.bz2'.
> >
> > 13 (primitive-load
> >
> > "/gnu/store/rsfj0ksp0jxw3cqkhyjjv0bffbiazg1m-compute-guix-
> >
> > derivation")
>
> To investigate the issue, this log file is required.
>
> Greetings,
>
> Maxime.
[-- Attachment #2: mmafhpmi83ssxg860wd93z9yhhhk5w-gcc-10.3.0.drv.bz2 --]
[-- Type: application/x-bzip, Size: 489011 bytes --]
next prev parent reply other threads:[~2022-01-25 0:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-24 18:28 bug#53511: guix pull command fails xdrcft56 via Bug reports for GNU Guix
2022-01-24 21:25 ` Maxime Devos
2022-01-24 23:35 ` xdrcft56 via Bug reports for GNU Guix [this message]
2022-01-25 7:59 ` Maxime Devos
2022-01-25 18:32 ` xdrcft56 via Bug reports for GNU Guix
2022-01-26 18:59 ` xdrcft56 via Bug reports for GNU Guix
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='HUlrLGynICEibzthGimGKkW6pAdXH50Ywc_PIpNrFjNayqEvcjYNmTLxpU_dgVYmlzHKZESPV6WszqT2wcrwHl0pDgVTAs72_aeoK0TX384=@protonmail.com' \
--to=bug-guix@gnu.org \
--cc=53511@debbugs.gnu.org \
--cc=maximedevos@telenet.be \
--cc=xdrcft56@protonmail.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).