From: Christopher Baines <mail@cbaines.net>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: Heads-up: “pre-push” Git hook updated
Date: Thu, 04 Jun 2020 19:33:28 +0100 [thread overview]
Message-ID: <87a71i8yvb.fsf@cbaines.net> (raw)
In-Reply-To: <87v9k7cann.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1873 bytes --]
Ludovic Courtès <ludo@gnu.org> writes:
> Hi,
>
> Christopher Baines <mail@cbaines.net> skribis:
>
>> So, I think make authenticate dislikes the naming I use for Git remotes,
>> in particular I don't have an origin remote.
>>
>> → make authenticate
>> Compiling Scheme modules...
>> Authenticating Git checkout...
>> Authenticating d68de95 to 776409c (0 commits)...
>> Backtrace:
>> In ice-9/boot-9.scm:
>> 1736:10 10 (with-exception-handler _ _ #:unwind? _ # _)
>> In unknown file:
>> 9 (apply-smob/0 #<thunk 7f4b2fed8940>)
>> In ice-9/boot-9.scm:
>> 718:2 8 (call-with-prompt _ _ #<procedure default-prompt-handle…>)
>> In ice-9/eval.scm:
>> 619:8 7 (_ #(#(#<directory (guile-user) 7f4b2fafaf00>)))
>> 293:34 6 (_ #(#(#(#(#(#(#(#(#(#(#<…> …) …) …) …) …) …) …) …) …) …))
>> In guix/progress.scm:
>> 71:36 5 (call-with-progress-reporter _ _)
>> In ice-9/eval.scm:
>> 619:8 4 (_ #(#(#(#<directory (guile-user) 7f4b2fafaf00>) # …) #))
>> 626:19 3 (_ #(#(#(#<directory (guile-user) 7f4b2fafaf00>) # …) #))
>> 293:34 2 (_ #(#(#<directory (guile-user) 7f4b2fafaf00>) #<git…> …))
>> In git/branch.scm:
>> 101:8 1 (_ _ _ _)
>> In git/bindings.scm:
>> 77:2 0 (raise-git-error _)
>>
>> git/bindings.scm:77:2: In procedure raise-git-error:
>> Git error: cannot locate remote-tracking branch 'origin/keyring'
>>
>> make: *** [Makefile:5965: authenticate] Error 1
>>
>>
>> I tried renaming my savannah remote to origin, and then it seemed to
>> work. Any ideas?
>
> Yeah, that’s a problem Tobias reported as well.
>
> In <https://issues.guix.gnu.org/41653> I change it to just use the local
> ‘keyring’ branch. That also requires you to set things up
> appropriately, but I think that’s hard to avoid no?
Great, that sounds good :)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 962 bytes --]
next prev parent reply other threads:[~2020-06-04 18:34 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-22 20:44 Updating the “pre-push” Git hook Ludovic Courtès
2020-05-22 21:17 ` Leo Famulari
2020-05-24 7:27 ` Ricardo Wurmus
2020-05-24 21:44 ` Ludovic Courtès
2020-05-25 9:50 ` Ricardo Wurmus
2020-05-25 22:04 ` Ludovic Courtès
2020-05-24 6:41 ` Efraim Flashner
2020-05-24 21:45 ` Ludovic Courtès
2020-05-25 5:50 ` Efraim Flashner
2020-05-25 21:31 ` Ludovic Courtès
2020-05-25 20:13 ` Vagrant Cascadian
2020-05-25 21:37 ` Ludovic Courtès
2020-05-26 16:41 ` Leo Famulari
2020-05-29 16:45 ` Heads-up: “pre-push” Git hook updated Ludovic Courtès
2020-05-29 17:07 ` Pierre Neidhardt
2020-05-29 18:39 ` Christopher Baines
2020-06-04 11:50 ` Ludovic Courtès
2020-06-04 18:33 ` Christopher Baines [this message]
2020-06-08 18:41 ` Vagrant Cascadian
2020-06-09 15:46 ` Ludovic Courtès
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=87a71i8yvb.fsf@cbaines.net \
--to=mail@cbaines.net \
--cc=guix-devel@gnu.org \
--cc=ludo@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).