GIT to GIT bzr push Fails "funny ref 'None' remotely"

Bug #690547 reported by Jordan Farrell
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Bazaar Git Plugin
Fix Released
Medium
Jelmer Vernooij

Bug Description

Local GIT to a Remote GIT Push
Run command: bzr push
error: refusing to create funny ref 'None' remotely
bzr: ERROR: None failed to update
Using saved push location:
git+ssh://<email address hidden>/wolfrage-telepathy/otr.git

GIT status in Bazaar: Working tree is up to date at revision 2139.

GIT status from GIT:
# On branch OTR
# Your branch and 'cosimoc/e2e-encryption' have diverged,
# and have 625 and 52 different commit(s) each, respectively.
#
nothing to commit (working directory clean)

Ubuntu 10.10 32bit.
bzr-git is installed.
Bazaar Explorer Version 1.1.0
QBzr 0.19.1, bzrlib 2.2.1, PyQt 4.7.4, Qt 4.7.0, Python 2.6.6

Revision history for this message
Jordan Farrell (feralbytes) wrote :

Log File with various GIT errors attached.

Revision history for this message
Jordan Farrell (feralbytes) wrote :

This bug also causes bzr to delete the repository on gitorious. I don't no why but I tried it with a error free GIT repository and it deleted the existing branch on gitorious, which forced me to push the branch back using git from the command line. Because it deletes remote repositories that are receiving a push I would make this a little more critical, because that could really hurt some one's project.

Revision history for this message
Jelmer Vernooij (jelmer) wrote :

That happens because we don't set the right ref name, and the ref name we do specify is invalid

When support for colocated branches lands, this will automatically be fixed.

Changed in bzr-git:
status: New → Triaged
importance: Undecided → Medium
Jelmer Vernooij (jelmer)
Changed in bzr-git:
status: Triaged → Fix Released
status: Fix Released → Fix Committed
assignee: nobody → Jelmer Vernooij (jelmer)
milestone: none → 0.6.3
Jelmer Vernooij (jelmer)
Changed in bzr-git:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.