debian packaging metadata: a dependency on pyasn1 #1095

New Issue

tahoe-lafs · 2010-06-22T09:16:20Z

arthur commented

2010-06-22 09:16:20 +00:00

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

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

tahoe-lafs added the

labels 2010-06-22 09:16:20 +00:00

tahoe-lafs added this to the 1.7.1 milestone 2010-06-22 09:16:20 +00:00

davidsarah commented

2010-07-17 05:44:06 +00:00

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

tahoe-lafs added

packaging

and removed

unknown

labels 2010-07-17 05:44:06 +00:00

tahoe-lafs modified the milestone from 1.7.1 to soon

2010-07-17 05:44:06 +00:00

zooko commented

2010-11-12 11:32:28 +00:00

I think should be fixed in [misc/debian/control.sid]source:trunk/misc/debian/control.sid@4054. 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.)

I think should be fixed in [misc/debian/control.sid]source:trunk/misc/debian/control.sid@4054. How should it be tested? We already have Debian buildslaves which test the building of .deb's (see the "Debian Waterfall" on [the Buildbot](http://tahoe-lafs.org/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](http://www.netfort.gr.jp/~dancer/software/pbuilder-doc/pbuilder-doc.html) 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.)

zooko changed title from ~~Have a dependency on pyasn1~~ to debian packaging metadata: a dependency on pyasn1

2010-11-12 11:32:28 +00:00

zooko commented

2011-01-16 03:57:43 +00:00

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?

zooko modified the milestone from soon to 1.8.2

2011-01-16 03:57:43 +00:00

warner commented

2011-01-17 07:44:47 +00:00

I'm going to add python-twisted-conch instead of python-pyasn1, since that transitively includes both pyasn1 and python-crypto.

I'm going to add `python-twisted-conch` instead of `python-pyasn1`, since that transitively includes both pyasn1 and `python-crypto`.

Brian Warner <warner@lothar.com> commented

2011-01-17 07:45:47 +00:00

In changeset:1e377c2225bf81aa:

debian/control: add python-twisted-conch to dependencies. Closes #1095.

In changeset:1e377c2225bf81aa: ``` debian/control: add python-twisted-conch to dependencies. Closes #1095. ```

tahoe-lafs added the

fixed

label 2011-01-17 07:45:47 +00:00

Brian Warner <warner@lothar.com> closed this issue

2011-01-17 07:45:47 +00:00

Brian Warner <warner@lothar.com> commented

2011-01-20 10:04:59 +00:00

In [4978/ticket1306]:

debian/control: add python-twisted-conch to dependencies. Closes #1095.

In [4978/ticket1306]: ``` debian/control: add python-twisted-conch to dependencies. Closes #1095. ```

Sign in to join this conversation.

No Label

LeastAuthority.com automation

code-frontend-ftp-sftp

code-frontend-magic-folder

somebody else's problem

No Milestone

No Assignees

3 Participants

Notifications

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Reference: tahoe-lafs/trac-2024-07-25#1095