Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error: repository has at least one unnamed head #50

Open
nschloe opened this issue Jan 5, 2015 · 3 comments
Open

Error: repository has at least one unnamed head #50

nschloe opened this issue Jan 5, 2015 · 3 comments

Comments

@nschloe
Copy link

nschloe commented Jan 5, 2015

When hg-cloning Octave, everything goes fine:

$ hg clone http://www.octave.org/hg/octave upstream
real URL is http://hg.savannah.gnu.org/hgweb/octave
requesting all changes
adding changesets
adding manifests
adding file changes
added 19535 changesets with 116074 changes to 12685 files (+1 heads)
updating to bookmark @
real URL is http://hg.savannah.gnu.org/hgweb/octave/gnulib-hg
cloning subrepo gnulib-hg from http://www.octave.org/hg/octave/gnulib-hg
requesting all changes
adding changesets
adding manifests
adding file changes
added 17763 changesets with 95689 changes to 11138 files (+13 heads)
3114 files updated, 0 files merged, 0 files removed, 0 files unresolved

so it seems the remote repo is intact. git-hg however fails with

$ git-hg clone http://www.octave.org/hg/octave
Initialized empty Git repository in /home/nschloe/software/octave/octave/.git/
real URL is http://hg.savannah.gnu.org/hgweb/octave
requesting all changes
adding changesets
adding manifests
adding file changes
added 19535 changesets with 116074 changes to 12685 files (+1 heads)
Initialized empty Git repository in /home/nschloe/software/octave/octave/.git/hgremote/
Error: repository has at least one unnamed head: hg r15563
fatal: Couldn't find remote ref gui-release
fatal: The remote end hung up unexpectedly
@dan-passaro
Copy link

I just ran into the same error today. I might dive into it later because we use hg at work and using hg itself is starting to drive me crazy. Even if I can't figure out how to patch the issue, I'll at least change the error reporting to use the commit hash instead of the revision number... (or try to, anyway)

@ndevenish
Copy link

Just ran into this same issue with the Hugin repository;

$ git hg clone http://hg.code.sf.net/p/hugin/hugin hugin-hugin
Error: repository has at least one unnamed head

@ndevenish
Copy link

However, I just discovered that git-hg actually supports fast-exports --force flag, so this works:

$ git hg clone --force http://hg.code.sf.net/p/hugin/hugin hugin-hugin

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants