maemo.org Bugzilla – Bug 7936
clone of /modest/wpeditor.git fails with: remote HEAD refers to nonexistent ref, unable to checkout.
Last modified: 2010-01-19 19:23:10 UTC
You need to log in before you can comment on or make changes to this bug.
Maybe someone can explain how this kind of thing happens (for those of us using GIT for the first time). [sbox-FREMANTLE_ARMEL: ~/bugfixes] > git clone git://gitorious.org/modest/wpeditor.git Initialize wpeditor/.git Initialized empty Git repository in /home/odin/bugfixes/wpeditor/.git/ remote: Counting objects: 50, done. remote: Compressing objects: 100% (46/46), done. remote: Total 50 (delta 11), reused 0 (delta 0) Receiving objects: 100% (50/50), 109.76 KiB, done. Resolving deltas: 100% (11/11), done. warning: remote HEAD refers to nonexistent ref, unable to checkout. [sbox-FREMANTLE_ARMEL: ~/bugfixes] > cat wpeditor/.git/HEAD ref: refs/heads/master [sbox-FREMANTLE_ARMEL: ~/bugfixes] > find wpeditor/ wpeditor/ wpeditor/.git wpeditor/.git/HEAD wpeditor/.git/description wpeditor/.git/logs wpeditor/.git/logs/refs wpeditor/.git/logs/refs/remotes wpeditor/.git/logs/refs/remotes/origin wpeditor/.git/logs/refs/remotes/origin/modest wpeditor/.git/logs/refs/remotes/origin/upstream wpeditor/.git/hooks wpeditor/.git/hooks/post-commit wpeditor/.git/hooks/update wpeditor/.git/hooks/commit-msg wpeditor/.git/hooks/post-receive wpeditor/.git/hooks/prepare-commit-msg wpeditor/.git/hooks/pre-commit wpeditor/.git/hooks/pre-applypatch wpeditor/.git/hooks/post-update wpeditor/.git/hooks/pre-rebase wpeditor/.git/hooks/applypatch-msg wpeditor/.git/branches wpeditor/.git/refs wpeditor/.git/refs/remotes wpeditor/.git/refs/remotes/origin wpeditor/.git/refs/remotes/origin/modest wpeditor/.git/refs/remotes/origin/upstream wpeditor/.git/refs/heads wpeditor/.git/refs/tags wpeditor/.git/config wpeditor/.git/objects wpeditor/.git/objects/pack wpeditor/.git/objects/pack/pack-092273fcbf781e1593c3759cc85e28eb734ad66b.pack wpeditor/.git/objects/pack/pack-092273fcbf781e1593c3759cc85e28eb734ad66b.idx wpeditor/.git/objects/pack/pack-092273fcbf781e1593c3759cc85e28eb734ad66b.keep wpeditor/.git/objects/info wpeditor/.git/info wpeditor/.git/info/exclude That is the file scructure obtained before the GIT "warning" aborted ! smells more like an error to me than a warning. timeless_mbp from IRC cited a link: http://www.mail-archive.com/gitorious@googlegroups.com/msg00228.html I think someone with read-write GIT access needs to change something ?
Try this directly after your failed clone attempt: [sbox-FREMANTLE_ARMEL: ~/bugfixes] > cd wpeditor [sbox-FREMANTLE_ARMEL: ~/bugfixes] > git branch -a origin/modest origin/upstream [sbox-FREMANTLE_ARMEL: ~/bugfixes] > git checkout -b modest origin/modest [sbox-FREMANTLE_ARMEL: ~/bugfixes] > git branch * modest
Yes after running these 4 commands the package source tree appears in the top level directory. So this workaround works, so just the repo to tweak/fix. For reference the output of running this commands by me looked more like: [sbox-FREMANTLE_ARMEL: ~/bugfixes] > cd wpeditor [sbox-FREMANTLE_ARMEL: ~/bugfixes/wpeditor] > git branch -a origin/modest origin/upstream [sbox-FREMANTLE_ARMEL: ~/bugfixes/wpeditor] > git checkout -b modest origin/modest warning: You appear to be on a branch yet to be born. warning: Forcing checkout of origin/modest. Branch modest set up to track remote branch refs/remotes/origin/modest. Switched to a new branch "modest" [sbox-FREMANTLE_ARMEL: ~/bugfixes/wpeditor] > git branch * modest
This has been fixed by jdapena@igalia.com (Modest maintainer???) on 14-Jan-2010.