unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Ada Stevenson <adanskana@gmail.com>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: Disabling authentication checks for tests in local Guix checkouts
Date: Mon, 17 Jun 2024 15:05:57 +0200	[thread overview]
Message-ID: <87zfrj7m8a.fsf@gnu.org> (raw)
In-Reply-To: <d4a6746a-1ea7-d272-e29b-ce75bcb9cf9e@gmail.com> (Ada Stevenson's message of "Mon, 10 Jun 2024 06:20:10 +0000")

Hi Ada,

Ada Stevenson <adanskana@gmail.com> skribis:

> I'm currently trying to help test the changes to GRUB submitted in
> issue #71348[1]. Unfortunately, `make check`, whilst building the
> local Guix channel, authenticates every commit. That means commits not
> signed by people in `guix-authorizations` will stop the channel from
> building and prevents running any of the tests.

Bummer.  :-(

> I have tried to fix the issue by writing a patch:

This patch looks like the right thing to do.

I’m not sure how to integrate it though: in the general case, we
probably want to keep authentication enabled by default, but how to
allow users to easily disable it when using a personal checkout?

> Initially this seems like it works, as it starts to index all of the
> commits in the local checkout, which didn't occur beforehand, instead
> immediately giving a `Git error: cannot locate remote-tracking branch
> 'origin/keyring'` (I've run `git fetch -a`, and my Savannah remote is
> called `origin`).

Guix caches clones under ~/.cache/guix/checkout.  It may be that there’s
a clone of your local repo there, but that the clone itself lack a copy
of the ‘keyring’ branch?  (You can run ‘git fetch -a’ in there.)

Thanks for testing!

Ludo’.


  reply	other threads:[~2024-06-17 13:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-10  6:20 Disabling authentication checks for tests in local Guix checkouts Ada Stevenson
2024-06-17 13:05 ` Ludovic Courtès [this message]
2024-06-17 14:02   ` Suhail Singh
2024-06-17 21:52     ` Ludovic Courtès
2024-06-18  2:36       ` Suhail Singh
2024-06-18  8:25   ` Ada Stevenson

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=87zfrj7m8a.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=adanskana@gmail.com \
    --cc=guix-devel@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).