svn-push to a new branch in svn trips assert in commit
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Bazaar Subversion Plugin |
Fix Released
|
Medium
|
Jelmer Vernooij |
Bug Description
In an attempt to first store the diverged revisions in an svn branch before merging that into the trunk, I thought to use svn-push repo/branches/
The traceback below is on copy of the actual repo to prevent further messing up.
bzr svn-push file://
bzr: ERROR: exceptions.
Traceback (most recent call last):
File "/home/
return run_bzr(argv)
File "/home/
ret = run(*run_argv)
File "/home/
return self.run(
File "/home/
_override_
File "/home/
override_
File "/home/
push(
File "/home/
override_
File "/home/
revid = builder.
File "/home/
assert not self.push_metadata or self._new_
AssertionError
bzr 1.10dev on python 2.5.2 (linux2)
arguments: ['/home/
encoding: 'UTF-8', fsenc: 'UTF-8', lang: 'en_US.UTF-8'
plugins:
bzrtools /home/wouter/
dbus /usr/lib/
gtk /home/wouter/
launchpad /home/wouter/
qbzr /home/wouter/
rebase /home/wouter/
svn /home/wouter/
upload /home/wouter/
vimdiff /home/wouter/
*** Bazaar has encountered an internal error.
Please report a bug at https:/
including this traceback, and a description of what you
were doing when the error occurred.
After this, svn log --stop-on-copy on the spitfire4 branch mentions:
r7745 | wouter | 2008-11-24 18:40:44 +0100 (Mon, 24 Nov 2008) | 1 line
Add doxyfile for spitfire.
-------
Which is the first commit after diverging from trunk.
Changed in bzr-svn: | |
milestone: | none → 0.5.0 |
status: | Triaged → Fix Released |
Can you perhaps print the variables in that assert?