unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
To: Julius Schwartzenberg <julius.schwartzenberg@gmail.com>
Cc: 60207@debbugs.gnu.org
Subject: bug#60207: Bug report
Date: Sat, 24 Dec 2022 22:40:52 +0100	[thread overview]
Message-ID: <87tu1kzdi3.fsf@pelzflorian.de> (raw)
In-Reply-To: <05cafc66-0812-4134-58d6-5b53814e3c11@gmail.com> (Julius Schwartzenberg's message of "Fri, 23 Dec 2022 21:00:49 +0100")

Hello Julius.

Julius Schwartzenberg <julius.schwartzenberg@gmail.com> writes:
> 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.

Indeed, but upgrading without compiling will be easier with bordeaux.
(Probably it would also have been possible to download guix 1.4.0
manually and then insert that into the store with `guix download` or
so.)


> […]
> 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?

Yes there is a way.  Look at the output from `guix weather` (see
<https://guix.gnu.org/en/manual/devel/en/html_node/Invoking-guix-weather.html>
in the English manual); if substitute coverage is bad, you could wait a
few days or maybe look at `guix build --log-file` if compilation fails
at the build farm (see
<https://guix.gnu.org/en/manual/devel/en/html_node/Additional-Build-Options.html>).

If you want `guix pull` without compiling, then look at
<https://guix.gnu.org/en/manual/devel/en/html_node/Channels-with-Substitutes.html>.

I hope it helps.

Regards,
Florian




  reply	other threads:[~2022-12-24 21:42 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
2022-12-24 21:40         ` pelzflorian (Florian Pelz) [this message]
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

  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=87tu1kzdi3.fsf@pelzflorian.de \
    --to=pelzflorian@pelzflorian.de \
    --cc=60207@debbugs.gnu.org \
    --cc=julius.schwartzenberg@gmail.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).