From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 11061] New: support/download: git version=master broken
Date: Tue, 05 Jun 2018 15:27:08 +0000 [thread overview]
Message-ID: <bug-11061-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=11061
Bug ID: 11061
Summary: support/download: git version=master broken
Product: buildroot
Version: 2018.05
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
Assignee: unassigned at buildroot.uclibc.org
Reporter: posted at heine.so
CC: buildroot at uclibc.org
Target Milestone: ---
Hi,
since the latest rework in the git downloader component setting the version to
the 'master' branch is not working anymore.
The error I see:
Could not fetch special ref 'master'; assuming it is not special.
Commit 'master' does not exist in this repository
using another branch is working fine. If I use another branch first and then
change the package to master it is switching the branch just fine and builds.
I tried some analysis:
When I use the command from [1] I get:
> git fetch origin master:master
fatal: Refusing to fetch into current branch refs/heads/master of non-bare
repository
fatal: The remote end hung up unexpectedly
>git rev-parse --verify "master^{commit}"
fatal: Needed a single revision
So there seems to be a clash between the local master and the remote master in
this case.
As said before, all this works when I first start the repo creation with
another branch and then switch to master.
Regards,
Michael
[1] https://git.buildroot.org/buildroot/tree/support/download/git#n125
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2018-06-05 15:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-05 15:27 bugzilla at busybox.net [this message]
2018-06-05 15:38 ` [Buildroot] [Bug 11061] support/download: git version=master broken bugzilla at busybox.net
2018-06-05 15:48 ` bugzilla at busybox.net
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-11061-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@busybox.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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.