debian packages for pycryptopp #210

New Issue

warner · 2007-11-15T20:43:57Z

warner commented

2007-11-15 20:43:57 +00:00

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.

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.

warner added the

labels 2007-11-15 20:43:57 +00:00

warner added this to the 0.7.0 milestone 2007-11-15 20:43:57 +00:00

warner self-assigned this 2007-11-15 20:43:57 +00:00

warner commented

2007-11-19 19:19:57 +00:00

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

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

warner added the

fixed

label 2007-11-19 19:19:57 +00:00

warner closed this issue

2007-11-19 19:19:57 +00:00

Sign in to join this conversation.