Ezbzr

release fails with unexpected argument branch

Bug #392301 reported by Tim Powell
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ezbzr
Fix Released
Critical
Unassigned

Bug Description

This causes release to fail completely. The full traceback shows:

File "/usr/lib/python2.5/site-packages/bzrlib/plugins/ezbzr/release.py", line 171, in run
   merge_cmd.run(branch=branch_base, revision=revision)

EZBzr's release calls the bzr internal merge command. It appears that it changed the name of the argument from branch to location.

Revision history for this message
Tim Powell (theuiguy) wrote :

It looks like we could fix this by not using a named argument. That could make ezbzr compatible with earlier and later versions of bzr, I believe. (Making the assumption that this is the only problem with it in bzr 1.16.)

Changed in ezbzr:
importance: Undecided → Critical
status: New → In Progress
Revision history for this message
Tim Powell (theuiguy) wrote :

Fixed on trunk

Changed in ezbzr:
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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