The debian patches from lp:debian/pycryptopp don't apply to trunk
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
pycryptopp (Debian) |
Fix Released
|
Unknown
|
|||
pycryptopp (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Trunk has changed (for the better) so that now these patches are unnecessary and no longer apply:
dpkg-source: warning: patches have not been applied, applying them now (use --no-preparation to override)
dpkg-source: info: applying move_testvector
dpkg-source: info: applying do_not_
dpkg-source: error: LC_ALL=C patch -t -F 0 -N -p1 -u -V never -g0 -E -b -B .pc/do_
generate_
patching file setup.py
Hunk #1 FAILED at 226.
1 out of 1 hunk FAILED -- saving rejects to file setup.py.rej
patching file setup.cfg
Hunk #1 FAILED at 10.
1 out of 1 hunk FAILED -- saving rejects to file setup.cfg.rej
dpkg-buildpackage: error: dpkg-source -i -I --before-build pycryptopp-808+6 gave error exit status 1
debuild: fatal error at line 1348:
dpkg-buildpackage -rfakeroot -d -us -uc -i -I -S failed
bzr: ERROR: Failed to build the source package
Changed in pycryptopp (Debian): | |
importance: | Undecided → Unknown |
status: | New → Unknown |
Changed in pycryptopp (Debian): | |
status: | Unknown → New |
Changed in pycryptopp (Debian): | |
status: | New → Fix Released |
I made some patches that fix this bug and let the current trunk of
pycryptopp build with the debian packaging plus my patches. You can
see my patches here:
https:/ /code.launchpad .net/~zooko/ pycryptopp/ debian
And the launchpad autobuilder using those patches here:
https:/ /code.launchpad .net/~tahoe- lafs/+recipe/ pycryptopp- daily