unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Vitaliy Shatrov <guix.vits@disroot.org>
To: 43238@debbugs.gnu.org
Subject: bug#43238: `guix system build -n` to be more informative (builds/substitutes)
Date: Sun, 06 Sep 2020 17:30:23 +0700	[thread overview]
Message-ID: <87sgbv5ha8.fsf@disroot.org> (raw)

Hello Guix.

I did:
`guix system build -n config.scm`

I get a message, something like:
"3 packages (guix, modules, and ?) would be downloaded."

I ran `sudo guix system build config.scm`.  Guix told me it will build
the linux kernel.  It was unexpected.

The `guix system build/reconfigure` upgrades the daemon first. Right?

So, if `guix` cannot know beforehand will the User get any substitutes..
Maybe:
   * `guix` should stop and ask in case there is a build ahead?
   * add a separate 'update-daemon-only' command (or flag) to `system`?


Background:
With `update-daemon-only`, one can just walk away.  Then look-up, if any
builds are ahead.  Of course i understood that the system-wide config
should be keept minimal.  So not that big trouble: just i had an
substitute offered to me (for kernel), but (as `system build -n` didn't
warned me) decided to not use it (as i thought the kernel will not be
updated).  When i found out that kernel actually going to be build, i
canceled it.  Then switched to kernel that has substitute (same config,
different hash).


---
Thank You for the attention, Vitaliy.







             reply	other threads:[~2020-09-06 10:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-06 10:30 Vitaliy Shatrov [this message]
2020-09-06 10:43 ` bug#43238: `guix system build -n` to be more informative (builds/substitutes) Ricardo Wurmus
2020-09-06 13:38 ` Vitaliy Shatrov
2020-09-06 19:58 ` Mark H Weaver

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=87sgbv5ha8.fsf@disroot.org \
    --to=guix.vits@disroot.org \
    --cc=43238@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).