From: Kyle Meyer <kyle@kyleam.com>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: "Ludovic Courtès" <ludo@gnu.org>, 49252@debbugs.gnu.org
Subject: [bug#49252] [PATCH] Channels defaulting to HEAD instead of ‘master’
Date: Sun, 08 Aug 2021 19:08:06 -0400 [thread overview]
Message-ID: <87mtpr8rhl.fsf@kyleam.com> (raw)
In-Reply-To: <87tuk0kpoz.fsf@elephly.net>
Ricardo Wurmus writes:
> For what it’s worth I found the same kind of problem when
> importing an R package from Github:
>
> ./pre-inst-env guix import cran -a git
> https://github.com/ImmuneDynamics/Spectre
>
> Here’s the error backtrace:
[...]
>
> ice-9/boot-9.scm:1685:16: In procedure raise-exception:
> Git error: reference 'refs/remotes/origin/HEAD' not found
> --8<---------------cut here---------------end--------------->8---
>
>> Presumably we have a server-side setup issue at Savannah?
>
> I think it might be a repository setting rather than a server
> setting as other Github repositories work, yet this one repo on
> Github does not.
Hmm, I'm not sure what's going on here, but, as with
<https://git.savannah.gnu.org/git/guix.git>, if I clone the above repo
via `git clone', refs/remotes/origin/HEAD is there:
$ git ls-remote https://github.com/ImmuneDynamics/Spectre | grep HEAD
742ebc4bc09ce69b970eceb78291bdbf5229d20d HEAD
$ git clone https://github.com/ImmuneDynamics/Spectre && cd Spectre
$ git for-each-ref refs/remotes/origin | grep HEAD
742ebc4bc09ce69b970eceb78291bdbf5229d20d commit refs/remotes/origin/HEAD
prev parent reply other threads:[~2021-08-08 23:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-28 12:56 [bug#49252] [PATCH] Channels defaulting to HEAD instead of ‘master’ Ludovic Courtès
2021-07-09 0:38 ` Kyle Meyer
2021-08-04 15:04 ` Ludovic Courtès
2021-08-08 23:28 ` Kyle Meyer
2021-08-09 9:12 ` Ludovic Courtès
2021-08-10 2:10 ` Kyle Meyer
2021-08-10 8:04 ` Ludovic Courtès
2021-08-11 0:34 ` Kyle Meyer
2021-08-08 13:53 ` Ricardo Wurmus
2021-08-08 23:08 ` Kyle Meyer [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=87mtpr8rhl.fsf@kyleam.com \
--to=kyle@kyleam.com \
--cc=49252@debbugs.gnu.org \
--cc=ludo@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 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).