unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: Christopher Rodriguez <yewscion@gmail.com>, guix-devel@gnu.org
Subject: Re: Idea: fallback for guix pull?
Date: Mon, 05 Sep 2022 17:53:29 +0200	[thread overview]
Message-ID: <87sfl5rf5y.fsf@gmail.com> (raw)
In-Reply-To: <87bksxmdop.fsf@gmail.com>

Hi,

Sorry for the late reply.

On sam., 06 août 2022 at 14:12, Christopher Rodriguez <yewscion@gmail.com> wrote:
> I haven't looked at the code at all, but perhaps it would be useful to
> users of Guix if, upon a guix pull with a commit that fails to
> authenticate, guix pull would still pull up to the last in the chain of
> successfully authenticated commmits?
>
> Right now, it stops the entire operation if one commit from one channel
> fails to authenticate, which has value (and might be useful as a setting
> or flag, for those with greater security concerns or those maintaining
> the channel).
>
> But assuming the authentications are done in order, could we make the
> default an effective "pin" to the last authenticated commit? This is
> probably the way users /should/ deal with this kind of issue anyway
> (disable-authentication is worrisome), and having the default be this
> kind of fallback would make it so users are still able to pull other
> channels they might have, or at least update to the last "good" commit.

Indeed, authentications are done in order (see ’authenticate-commits’
from (guix git-authenticate)) but the failure raises an error (see
’authenticate-commit’).

Note that the Git repository is already updated.  So, some tweaks would
be necessary to implement your suggestion.  Well, I am not convinced the
use-case is worth the effort.

However, I agree that a channel failing (for whatever reason) should not
be blocking for pulling all the others.  As discussed in bug#57559 [1].


Cheers,
simon

1: <http://issues.guix.gnu.org/issue/57559>



      reply	other threads:[~2022-09-05 17:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-06 18:12 Idea: fallback for guix pull? Christopher Rodriguez
2022-09-05 15:53 ` zimoun [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=87sfl5rf5y.fsf@gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=yewscion@gmail.com \
    /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).