colo plugin 0.1.0 is not compatible with bzr 2.2.1

Bug #669041 reported by Alexander Belchenko
14
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Bazaar Windows Installers
Confirmed
High
Unassigned
bzr-colo
Fix Released
Undecided
Neil Martinsen-Burrell

Bug Description

I've installed bzr 2.2.1 from 2.2.1-3 standalone installer and tried to use colo plugin and had traceback:

D:\work\logic>bzr colo-fixup
bzr: ERROR: exceptions.TypeError: set_reference() takes exactly 4 arguments (3 given)

Traceback (most recent call last):
  File "bzrlib\commands.pyo", line 912, in exception_to_return_code
  File "bzrlib\commands.pyo", line 1112, in run_bzr
  File "bzrlib\commands.pyo", line 690, in run_argv_aliases
  File "bzrlib\commands.pyo", line 705, in run
  File "bzrlib\cleanup.pyo", line 135, in run_simple
  File "bzrlib\cleanup.pyo", line 165, in _do_with_cleanups
  File "D:/Program Files/Bazaar/plugins\colo\commands.py", line 595, in run
TypeError: set_reference() takes exactly 4 arguments (3 given)

bzr 2.2.1 on python 2.6.4 (Windows-XP-5.1.2600-SP2)
arguments: ['D:\\Program Files\\Bazaar\\bzr.EXE', 'colo-fixup']
encoding: 'cp1251', fsenc: 'mbcs', lang: None
plugins:
  bzrtools D:\Program Files\Bazaar\plugins\bzrtools [2.2.0]
  colo D:\Program Files\Bazaar\plugins\colo [0.1.0]
  launchpad D:\Program Files\Bazaar\plugins\launchpad [2.2.1]
  qbzr D:\Program Files\Bazaar\plugins\qbzr [0.19.2]
  rewrite D:\Program Files\Bazaar\plugins\rewrite [0.6.1]

*** Bazaar has encountered an internal error. This probably indicates a
    bug in Bazaar. You can help us fix it by filing a bug report at
        https://bugs.launchpad.net/bzr/+filebug
    including this traceback and a description of the problem.

Version of colo plugin 0.1.0 is incompatible with bzr 2.2.1. I'm sure installer should bundle colo 0.2.0 instead.

Changed in bzr-windows-installers:
status: New → Confirmed
importance: Undecided → High
Revision history for this message
Alexander Belchenko (bialix) wrote :

I can confirm that colo 0.2.0 from release tarball has fixed the issue.

Revision history for this message
Alexander Belchenko (bialix) wrote :

@Neil: to fix this in the windows-installers branch I need the way to point to specific revision in lp:bzr-colo to get 0.2.0 release. As I can see there is no corresponding tag in your branch. Can you add such tag or create separate release branch, please?

Changed in bzr-colo:
assignee: nobody → Neil Martinsen-Burrell (nmb)
status: New → Confirmed
Revision history for this message
Alexander Belchenko (bialix) wrote :

C:\work\Bazaar\bzr-windows-installers>bzr tags -d lp:bzr-colo
Connected (version 2.0, client Twisted)
Authentication (publickey) successful!
Secsh channel 1 opened.
0.0.2 64.2.2
0.1.0 79.1.1

Revision history for this message
Neil Martinsen-Burrell (nmb) wrote :

I pushed a tag to lp:trunk:

$ bzr tags -d lp:bzr-colo
0.0.2 64.2.2
0.1.0 79.1.1
0.2.0 92.1.1

Changed in bzr-windows-installers:
status: Confirmed → Fix Released
Changed in bzr-colo:
status: Confirmed → Fix Released
Changed in bzr-windows-installers:
status: Fix Released → Confirmed
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.