unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: "D. Birch" <d.s.j.birch@gmail.com>
To: 53645@debbugs.gnu.org
Subject: bug#53645: Unable to guix pull on pinebook pro
Date: Wed, 2 Feb 2022 08:47:26 +0000	[thread overview]
Message-ID: <CAJw6i1CZa0eG+pf3rk7q6nbcB7vGgW95uMGg1NXf-5DH=ue-zQ@mail.gmail.com> (raw)
In-Reply-To: <CAJw6i1B8MFaHR556bCEa0YkdP_K=jXYrtPkyatVBODBbNd8sQg@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 564 bytes --]

Thank-you for all the help.

I left the laptop ticking away again after adding 10G of swap.

I've attached the stdout and stderr, as before.

Things got much further and the system was building for the whole day, I
left it running overnight and in the morning hit another "bug".

I can't see where the build log is this time to attach.

I don't fully understand what guix pull does. If I was to run it again,
would everything begin from the start, or is there some chance re-running
it would pick up where it left off?

I'll try it shortly and find out I suppose.

[-- Attachment #1.2: Type: text/html, Size: 771 bytes --]

[-- Attachment #2: guix-pull-bug-03-attempt --]
[-- Type: application/octet-stream, Size: 451138 bytes --]

  parent reply	other threads:[~2022-02-02  8:51 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 [this message]
2022-02-02 22:35   ` Pierre Langlois
2022-02-03 10:21     ` D. Birch
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='CAJw6i1CZa0eG+pf3rk7q6nbcB7vGgW95uMGg1NXf-5DH=ue-zQ@mail.gmail.com' \
    --to=d.s.j.birch@gmail.com \
    --cc=53645@debbugs.gnu.org \
    /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).