From: raingloom <raingloom@riseup.net>
To: Andreas Enge <andreas@enge.fr>
Cc: Gottfried <gottfried@posteo.de>, help-guix@gnu.org
Subject: Re: guix package -u . --do-not-upgrade
Date: Wed, 11 May 2022 18:31:47 +0200 [thread overview]
Message-ID: <20220511183147.5c1ffe56@riseup.net> (raw)
In-Reply-To: <Ynqs7h6GYVNmh3iq@jurong>
On Tue, 10 May 2022 20:20:30 +0200
Andreas Enge <andreas@enge.fr> wrote:
> Am Tue, May 10, 2022 at 06:10:42PM +0000 schrieb Gottfried:
> > guix package --upgrade . --do-not-upgrade emacs vlc knotes (Can I
> > put 3 after each other)
>
> Yes, that works. (In any case, you can just give it a try. If you do
> not like the result, you can always do a "guix package --roll-back"!)
>
> Andreas
>
You can't un-transfer the bytes though. That matters on a metered
connection.
The better advice would be to run such commands with --dry-run, which
will print what would be done.
AFAIK it only downloads the list of substitutes, not any NARs.
prev parent reply other threads:[~2022-05-12 10:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-10 18:10 guix package -u . --do-not-upgrade Gottfried
2022-05-10 18:20 ` Andreas Enge
2022-05-11 16:31 ` raingloom [this message]
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=20220511183147.5c1ffe56@riseup.net \
--to=raingloom@riseup.net \
--cc=andreas@enge.fr \
--cc=gottfried@posteo.de \
--cc=help-guix@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.
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).