From: Csepp <raingloom@riseup.net>
To: 57315@debbugs.gnu.org
Subject: bug#57315: guix upgrade --dry-run output is basically useless
Date: Sun, 21 Aug 2022 08:39:02 +0200 [thread overview]
Message-ID: <87pmgu3xc6.fsf@riseup.net> (raw)
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.
This should go without saying, but this is pretty bad UX.
Is there something that can be done about this? The upgrade process on
less powerful machines is pretty awful currently.
Side note: I plan to work on a patch that adds an option to upgrade that
keeps everything that would require local building at its previous
version. Hopefully I won't need to use the --do-not-upgrade option
after that. Right now upgrading is a multi-hour manual process, which
honestly sucks. With that patch it would still take a while but at
least it would run automatically.
next reply other threads:[~2022-08-21 6:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-21 6:39 Csepp [this message]
2022-08-21 8:44 ` bug#57315: guix upgrade --dry-run output is basically useless bdju via Bug reports for GNU Guix
2022-08-31 9:25 ` Ludovic Courtès
2022-08-31 9:28 ` Ludovic Courtès
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
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=87pmgu3xc6.fsf@riseup.net \
--to=raingloom@riseup.net \
--cc=57315@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).