From: "D. Birch" <d.s.j.birch@gmail.com>
To: Pierre Langlois <pierre.langlois@gmx.com>
Cc: 53645@debbugs.gnu.org
Subject: bug#53645: Unable to guix pull on pinebook pro
Date: Thu, 3 Feb 2022 10:21:10 +0000 [thread overview]
Message-ID: <CAJw6i1BOpFtgPLuO4mdjW-Nqdj+7RJnfhhk=CrBq+v43r4W9Fw@mail.gmail.com> (raw)
In-Reply-To: <874k5gvqj7.fsf@gmx.com>
[-- Attachment #1.1: Type: text/plain, Size: 650 bytes --]
On Wed, 2 Feb 2022 at 22:42, Pierre Langlois <pierre.langlois@gmx.com>
wrote:
> That's strange that there isn't a log file to report, it looks like
> util-linux didn't build but I'm not sure. What you could try is to run
> `guix pull -v3' to enable more verbosity, and it should show build
> output for packages as it's building them.
> ...
> guix pull -v3 --commit=2641621 # Commit picked from the log file.
Tried my best not to top post ;)
I've attached the output from an attempt using a slight modification to the
command recommended above. The command I ran was
guix pull -v3 --commit=2641621 2>&1 | tee guix-pull-bug-verbose-01
Thank-you
[-- Attachment #1.2: Type: text/html, Size: 1013 bytes --]
[-- Attachment #2: guix-pull-bug-verbose-01 --]
[-- Type: application/octet-stream, Size: 303064 bytes --]
next prev parent reply other threads:[~2022-02-03 10:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-30 20:36 bug#53645: Unable to guix pull on pinebook pro D. Birch
2022-01-31 10:10 ` Maxime Devos
2022-01-31 18:58 ` D. Birch
2022-01-31 19:12 ` Maxime Devos
2022-01-31 19:57 ` Pierre Langlois
2022-02-02 8:47 ` D. Birch
2022-02-02 22:35 ` Pierre Langlois
2022-02-03 10:21 ` D. Birch [this message]
2022-02-03 15:56 ` Maxime Devos
2022-02-03 16:27 ` D. Birch
2022-02-03 16:36 ` D. Birch
2022-02-03 16:43 ` 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
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='CAJw6i1BOpFtgPLuO4mdjW-Nqdj+7RJnfhhk=CrBq+v43r4W9Fw@mail.gmail.com' \
--to=d.s.j.birch@gmail.com \
--cc=53645@debbugs.gnu.org \
--cc=pierre.langlois@gmx.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).