From: Julius Schwartzenberg <julius.schwartzenberg@gmail.com>
To: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
Cc: 60207@debbugs.gnu.org
Subject: bug#60207: Bug report
Date: Fri, 23 Dec 2022 21:00:49 +0100 [thread overview]
Message-ID: <05cafc66-0812-4134-58d6-5b53814e3c11@gmail.com> (raw)
In-Reply-To: <874jtozsk6.fsf@pelzflorian.de>
Op 21-12-2022 om 16:26 schreef pelzflorian (Florian Pelz):
> Oops, my mistake. You wrote your guix is at version 1.3.0, which is
> older than the bordeaux build farm.
No problem! I used the installation script just a few days earlier and I
presumed it would give me the latest of everything. I didn't imagine I
would need to do a 'guix pull' after running it. It seems I ran it at a
bad moment, just as 1.4.0 was about to be released.
> So how would you get an updated Guix? One way would be to delete /gnu
> and /var/guix and then just download and install the 1.4.0 version, but
> deleting would invalidate all links to the store.
I did this as I am working with essentially a fresh installation.
Unfortunately it is still not working out. While more packages seem to
be downloaded, some very large ones are still being compiled and this
simply ends up hanging my system.
Is there a way to enforce only binaries are fetched and compilation is
never attempted? Even if that means I might not always run the latest
version?
Thank you!
Best regards,
Julius
next prev parent reply other threads:[~2022-12-23 20:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-19 17:48 bug#60207: Bug report Julius Schwartzenberg
2022-12-20 9:34 ` pelzflorian (Florian Pelz)
2022-12-20 19:51 ` Julius Schwartzenberg
2022-12-21 15:26 ` pelzflorian (Florian Pelz)
2022-12-23 20:00 ` Julius Schwartzenberg [this message]
2022-12-24 21:40 ` pelzflorian (Florian Pelz)
2022-12-25 15:35 ` Julius Schwartzenberg
2022-12-26 12:09 ` bug#60207: ci build of latest guix for armhf pelzflorian (Florian Pelz)
2022-12-28 18:14 ` Christopher Baines
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=05cafc66-0812-4134-58d6-5b53814e3c11@gmail.com \
--to=julius.schwartzenberg@gmail.com \
--cc=60207@debbugs.gnu.org \
--cc=pelzflorian@pelzflorian.de \
/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.