From: "Ludovic Courtès" <ludo@gnu.org>
To: Csepp <raingloom@riseup.net>
Cc: 57315@debbugs.gnu.org
Subject: bug#57315: guix upgrade --dry-run output is basically useless
Date: Wed, 31 Aug 2022 11:28:26 +0200 [thread overview]
Message-ID: <87k06odao5.fsf@gnu.org> (raw)
In-Reply-To: <87pmgu3xc6.fsf@riseup.net> (Csepp's message of "Sun, 21 Aug 2022 08:39:02 +0200")
Hi,
Csepp <raingloom@riseup.net> skribis:
> I'd like to figure out what Guix will try to build before I run an
> upgrade on my netbook, so I always use --dry-run. I'm pretty sure in
> the past it used to show more information, but today it just showed that
> it will download 20 megs, without saying what package that 20 megs are
> for, which ones will be built, which ones are downloaded, or anything
> useful at all.
>
> And now I see it's building Caja. Why did it not warn me beforehand?
> No idea.
I understand this is a source of confusion. It has to do with “grafts”
(which themselves are about applying security updates): if substitutes
for a package are missing, Guix has a partial view of the dependency
graph, which is why it can only tell you about extra builds/downloads
later on in the process (it does report them, only later).
(If you’re curious, see
<https://guix.gnu.org/en/blog/2020/grafts-continued/> for details.)
Thanks,
Ludo’.
next prev parent reply other threads:[~2022-08-31 9:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-21 6:39 bug#57315: guix upgrade --dry-run output is basically useless Csepp
2022-08-21 8:44 ` bdju via Bug reports for GNU Guix
2022-08-31 9:25 ` Ludovic Courtès
2022-08-31 9:28 ` Ludovic Courtès [this message]
2022-08-31 12:29 ` zimoun
2022-09-01 12:05 ` Ludovic Courtès
2022-09-01 17:19 ` zimoun
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=87k06odao5.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=57315@debbugs.gnu.org \
--cc=raingloom@riseup.net \
/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.