Problem with 0.9.7 and cvs in cvsps.py: sort() takes no keyword arguments (Python 2.3)

[mpaesold]

After upgrading from 0.9.6 to 0.9.7 I am seeing this backtrace when trying to run tailor for a CVS -> Mercurial conversion. Before the upgrade it worked flawlessly.

Traceback (most recent call last):
  File "/usr/lib/python2.3/site-packages/vcpx/source.py", line 110, in applyPendingChangesets
    res = self._applyChangeset(c)
  File "/usr/lib/python2.3/site-packages/vcpx/repository/cvsps.py", line 343, in _applyChangeset
    revs.sort(cmp=compare_cvs_revs)
TypeError: sort() takes no keyword arguments
13:39:45 [C] Upstream change application failed
Traceback (most recent call last):
  File "/usr/bin/tailor", line 35, in ?
    main()
  File "/usr/lib/python2.3/site-packages/vcpx/tailor.py", line 338, in main
    tailorizer()
  File "/usr/lib/python2.3/site-packages/vcpx/tailor.py", line 146, in __call__
    self.update()
  File "/usr/lib/python2.3/site-packages/vcpx/tailor.py", line 109, in update
    last, conflicts = dwd.applyPendingChangesets(
  File "/usr/lib/python2.3/site-packages/vcpx/dualwd.py", line 97, in applyPendingChangesets
    applied=applied)
  File "/usr/lib/python2.3/site-packages/vcpx/source.py", line 110, in applyPendingChangesets
    res = self._applyChangeset(c)
  File "/usr/lib/python2.3/site-packages/vcpx/repository/cvsps.py", line 343, in _applyChangeset
    revs.sort(cmp=compare_cvs_revs)
TypeError: sort() takes no keyword arguments

The config file:

[DEFAULT]
verbose = True
projects = pgjdbc

[pgjdbc]
source = cvs:pgjdbc
target = hg:pgjdbc
start-revision = INITIAL
root-directory = /home/mip/documents/tailor
state-file = tailor.state
subdir = pgjdbc.wc
patch-name-format=

[cvs:pgjdbc]
encoding = ISO-8859-1
module = pgjdbc
repository = :pserver:anonymous@gborg.postgresql.org:/usr/local/cvsroot/pgjdbc

[hg:pgjdbc]
repository = pgjdbc.hg

This is on CentOS 4, Python 2.3.4. Mercurial version is 0.9.3 (therefore I need tailor 0.9.6).

After looking at the history of cvsps, I now see that this is already fixed in the source repository: r1301. I still submit this issue, because I have not found another one describing the problem and someone else might look for a solution. Please just close the ticket. Thanks!

Best Regards Michael Paesold

[mpaesold]

Note: this is fixed in r1301.