debian packaging metadata: a dependency on pyasn1

[arthur]

After using the freshly built deb file :

$ tahoe
Traceback (most recent call last):
  File "/usr/bin/tahoe", line 2, in <module>
    from allmydata.scripts import runner
  File "/usr/lib/python2.5/site-packages/allmydata/scripts/runner.py", line 9, in <module>
    pkg_resources.require('allmydata-tahoe')
  File "/usr/lib/python2.5/site-packages/pkg_resources.py", line 626, in require
    needed = self.resolve(parse_requirements(requirements))
  File "/usr/lib/python2.5/site-packages/pkg_resources.py", line 524, in resolve
    raise DistributionNotFound(req)  # XXX put more info here
pkg_resources.DistributionNotFound: pyasn1>=0.0.8a

Work around is simply apt-get install python-pyasn1

[davidsarah]

If I understand correctly, this is to do with the debian packaging of Tahoe-LAFS, which is independent of the Tahoe-LAFS release process.

[zooko]

I think should be fixed in misc/debian/control.sid. How should it be tested? We already have Debian buildslaves which test the building of .deb's (see the "Debian Waterfall" on ​the Buildbot), but I guess those two buildslaves have pyasn1 installed, so they failed to detect this bug in control.sid. Could we use some sort of chroot to make sure -- oh, I know! ​pbuilder is for this. pbuilder is a tool to make sure that your build is not using any Debian packages other than the packages specified in your debian control file.

Created a new ticket (#1256) to be about setting up a pbuilder-managed buildbot step. (Or some other similar tool to pbuilder if you prefer.)