Changes between Initial Version and Version 2 of Ticket #1095


Ignore:
Timestamp:
2010-11-12T11:32:28Z (14 years ago)
Author:
zooko
Comment:

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.)

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #1095

    • Property Component changed from unknown to packaging
    • Property Summary changed from Have a dependency on pyasn1 to debian packaging metadata: a dependency on pyasn1
    • Property Owner changed from nobody to somebody
    • Property Milestone changed from 1.7.1 to soon
    • Property Keywords install pyasn1 debian added

  • Ticket #1095 – Description

    initial v2  
    11After using the freshly built deb file :
    22
     3{{{
    34$ tahoe
    45Traceback (most recent call last):
    … …  
    1213    raise DistributionNotFound(req)  # XXX put more info here
    1314pkg_resources.DistributionNotFound: pyasn1>=0.0.8a
    14 
     15}}}
    1516
    1617Work around is simply apt-get install python-pyasn1