From: ludo@gnu.org (Ludovic Courtès)
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel@gnu.org
Subject: Re: Upgrading packages with substitutes only (bug #26608)
Date: Mon, 19 Jun 2017 14:02:13 +0200 [thread overview]
Message-ID: <87vansw5h6.fsf@gnu.org> (raw)
In-Reply-To: <87injt7hzu.fsf@elephly.net> (Ricardo Wurmus's message of "Sun, 18 Jun 2017 11:38:45 +0200")
Ricardo Wurmus <rekado@elephly.net> skribis:
> Ludovic Courtès <ludo@gnu.org> writes:
>
>> BTW, should --only-substitutes filter out packages without a substitute,
>> or should it simply stop and report the list of missing substitutes
>> (after which the user could use --do-not-upgrade)?
>
> In my opinion “--only-substitutes” should stop and report a list.
> If it continued without complaining there could be problems:
>
> * partial upgrades could leave the profile in an unusable state
>
> * an attacker could use this to trick a user into thinking that they
> have all available updates
Agreed.
> On the other hand, it would make “--only-substitutes” less usable,
> because to actually perform work one would have to deal with the failure
> case.
IMO that’s OK. “--only-substitutes” would typically be for interactive
use, when you’re in a hurry and you Understand The Risks (click on the
checkbox ;-)). For unattended upgrades, I think one would want to
upgrade no matter what (assuming of course the build farm is not
completely broken, meaning that most substitutes are available.)
WDYT?
In the future I was also thinking that the build farm could tag Git
commits that it has fully built, and thus ‘guix pull’ could be told to
pull to the latest fully-built commit.
Ludo’.
next prev parent reply other threads:[~2017-06-19 12:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-16 19:28 Upgrading packages with substitutes only (bug #26608) Timothy Sample
2017-06-17 22:34 ` Ludovic Courtès
2017-06-18 9:38 ` Ricardo Wurmus
2017-06-18 16:11 ` Leo Famulari
2017-06-18 17:44 ` Timothy Sample
2017-06-18 21:44 ` Ricardo Wurmus
2017-06-19 0:23 ` Carlo Zancanaro
2017-06-19 17:33 ` Leo Famulari
2017-06-19 12:02 ` Ludovic Courtès [this message]
2017-06-19 17:25 ` Timothy Sample
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=87vansw5h6.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=rekado@elephly.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.