#210 closed task (fixed)

debian packages for pycryptopp

Reported by: warner Owned by: warner
Priority: major Milestone: 0.7.0
Component: packaging Version: 0.7.0
Keywords: debian Cc:
Launchpad Bug:

Description

We need .deb packages of pycryptopp to make the tahoe .deb packages at all usable, now that HEAD requires pycryptopp. The process will be similar to the one I used for debianizing zfec.

I think this needs to be done before the 0.7.0 release, otherwise the 0.7.0 debs will be unusable.

Change History (1)

comment:1 Changed at 2007-11-19T19:19:57Z by warner

  • Resolution set to fixed
  • Status changed from new to closed

done, for sid, etch, edgy, feisty, and gutsy. As usual we're skipping dapper, since it's too old to conveniently handle. I used the 'stdeb' plugin, by running 'py2dsc pycryptopp-0.2.6.tar.gz', which gave me a .orig.tar.gz, a .diff.gz, and a .dsc .

I then unpacked a source tree using those files and modified it as follows:

  • setup.py: remove the declared dependency upon darcs_setuptools, since that would require yet another debian package, and it's only actually needed to create a source tarball
  • setup.py: prefer /usr/include/crypto++ to /usr/include/cryptopp, since the recent debian change (to symlink /usr/include/cryptopp to crypto++) didn't also symlink the library files. The include/ symlink tricked our setup.py into thinking that it should look for /usr/lib/libcryptopp.a, which doesn't exist.
  • debian/control: declare a build dependency upon libcrypto++-dev

On edgy, I also had to modify the debian/control build-dependency on debhelper to allow it to be slightly older.

The resulting source package is named 'pycryptopp', and the binary package is named 'python-pycryptopp'.

Note: See TracTickets for help on using tickets.