While freezing bzr-2.2.5 from a natty machine with python-2.7.1+,
lp:testtools revno 244 and lp:subunit revno 151 I wasn't able to
run 'make check-dist-tarball'.
I had to revert to testtools-0.9.2 and subunit 0.0.6 and use
python2.6 to successfully run:
BZR_PLUGIN_PATH=-site make check-dist-tarball PYTHON=python2.6 | subunit2pyunit
Also, I've checked the versions used on pqm:
(pqm-amd64-new)pqm@cupuasso:~/pqm-workdir/bzr+ssh/new-pqm-test$ dpkg -l | grep subunit
ii libsubunit-perl 0.0.6-1~bazaar1.0.IS.10.04 perl parser and diff for Subunit streams
ii python-subunit 0.0.6-1~bazaar1.0.IS.10.04 unit testing protocol - Python bindings to g
ii subunit 0.0.6-1~bazaar1.0.IS.10.04 command line tools for processing Subunit st
(pqm-amd64-new)pqm@cupuasso:~/pqm-workdir/bzr+ssh/new-pqm-test$ dpkg -l | grep testtools
ii python-testtools 0.9.6-0~bazaar1.0.IS.8.04 Extensions to the Python unittest library
Targeting bzr itself for now.
The main risk here is that pqm upgrades subunit/testtools making landings on lp:bzr/2.0, lp:bzr/2.1 and lp:bzr/2.2 problematic.
We can either require that pqm is not upgraded (but for how long) , ask subunit and testtools maintainers to address the compatibility issue or fix 2.0, 2.1 and 2.2 to be compatible with more recent versions of subunit/testtools.
Or there may be an easier way :)