#1095 closed defect (fixed)
debian packaging metadata: a dependency on pyasn1
| Reported by: | arthur | Owned by: | warner |
|---|---|---|---|
| Priority: | major | Milestone: | 1.8.2 |
| Component: | packaging | Version: | 1.7β |
| Keywords: | install pyasn1 debian | Cc: | |
| Launchpad Bug: |
Description (last modified by zooko)
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
Change History (7)
comment:1 Changed at 2010-07-17T05:44:06Z by davidsarah
- Component changed from unknown to packaging
- Keywords install pyasn1 debian added
- Milestone changed from 1.7.1 to soon
- Owner changed from nobody to somebody
comment:2 Changed at 2010-11-12T11:32:28Z by zooko
- Description modified (diff)
- Summary changed from Have a dependency on pyasn1 to debian packaging metadata: a dependency on pyasn1
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.)
comment:3 Changed at 2011-01-16T03:57:43Z by zooko
- Milestone changed from soon to 1.8.2
Hm, even if we aren't going to set up a proper pbuilder-based test, then I guess we should probably fix this bug anyway for 1.8.2. Does some Debian-lover out there want to take this issue?
comment:4 Changed at 2011-01-17T07:22:41Z by warner
- Owner changed from somebody to warner
- Status changed from new to assigned
comment:5 Changed at 2011-01-17T07:44:47Z by warner
I'm going to add python-twisted-conch instead of python-pyasn1, since that transitively includes both pyasn1 and python-crypto.
comment:6 Changed at 2011-01-17T07:45:47Z by Brian Warner <warner@…>
- Resolution set to fixed
- Status changed from assigned to closed
In 1e377c2225bf81aa:
If I understand correctly, this is to do with the debian packaging of Tahoe-LAFS, which is independent of the Tahoe-LAFS release process.