From: Andreas Enge <andreas@enge.fr>
To: Andy Tai <atai@atai.org>
Cc: help-guix@gnu.org
Subject: Re: two questions on guix upgrade
Date: Tue, 16 Mar 2021 22:19:57 +0100 [thread overview]
Message-ID: <YFEg/VYOjG21Te1n@jurong> (raw)
In-Reply-To: <CAJsg1E-rcvYobTrQxpjVS=1ROW9A1RLR-B10vyVA=f=waqawZQ@mail.gmail.com>
Hello,
Am Tue, Mar 16, 2021 at 12:47:33PM -0700 schrieb Andy Tai:
> guix pull && guix package -u
this may not be what you are looking for, but my pedestrian way of doing
things is to do a "--dry-run" first:
guix package -n -u
(the "-u" must come last, or be replaced by "-u .").
That queries the substitute servers and shows a list of packages that would
be downloaded or built locally. And then I exclude the latter in a second
run with "--do-not-upgrade" if I feel a local build is too costly.
It is lacking in automation, however... At the same time, you know what is
updated and what needs another trial later.
Andreas
prev parent reply other threads:[~2021-03-16 21:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-16 19:47 two questions on guix upgrade Andy Tai
2021-03-16 20:43 ` Leo Famulari
2021-03-16 21:19 ` Andreas Enge [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=YFEg/VYOjG21Te1n@jurong \
--to=andreas@enge.fr \
--cc=atai@atai.org \
--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).