From: "Ludovic Courtès" <ludo@gnu.org>
To: Leo Famulari <leo@famulari.name>
Cc: 41764@debbugs.gnu.org
Subject: bug#41764: `make authenticate` fails to find the keyring branch
Date: Tue, 09 Jun 2020 18:16:00 +0200 [thread overview]
Message-ID: <87img0gqpr.fsf@gnu.org> (raw)
In-Reply-To: <20200608185404.GA2356@jasmine.lan> (Leo Famulari's message of "Mon, 8 Jun 2020 14:54:04 -0400")
Hi,
Leo Famulari <leo@famulari.name> skribis:
> I just tried pushing for the first time since installing the new
> pre-push hook that runs `make authenticate`.
>
> This failed with the following error:
>
> Git error: cannot locate remote-tracking branch 'keyring'
>
> However, `git branch --all` includes "remotes/origin/keyring".
>
> After I did `git checkout origin/keyring`, it worked.
Right, since commit 512b9e2da26968ebafdd47f701edd8fc3936d3e8, you have
to have a local ‘keyring’ branch.
> Let's update the manual section Commit Access with the recommended way
> to make this branch accessible to `make authenticate`. Maybe it should
> even do it automatically?
I don’t think it can do it automatically because it cannot guess what
the remote is called (Tobias reported an issue earlier because
“origin/keyring” was hard-coded and Tobias didn’t have an “origin”
remote.)
Regarding documentation, do you think it would suffice to say that one
needs to have a local ‘keyring’ branch tracking upstream’s?
Thanks,
Ludo’.
next prev parent reply other threads:[~2020-06-09 16:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-08 18:54 bug#41764: `make authenticate` fails to find the keyring branch Leo Famulari
2020-06-09 16:16 ` Ludovic Courtès [this message]
2020-10-24 12:49 ` Miguel Ángel Arruga Vivas
2020-10-24 15:02 ` Ludovic Courtès
2020-10-24 15:41 ` Miguel Ángel Arruga Vivas
2020-08-07 12:33 ` guix-vits via web
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=87img0gqpr.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=41764@debbugs.gnu.org \
--cc=leo@famulari.name \
/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).