I did, in fact, misunderstand the original request, on re-reading it I
see that the inclination is that the API has not been changed and
upstream has asserted as much. Reversing my position then, and marknig
this as Invalid in tahoe-lafs, and Confirmed in pycryptopp.
The next step would be for somebody to pick up the bug and actually
produce a debdiff or bzr merge proposal to update natty to this version.
** Changed in: pycryptopp (Ubuntu Natty)
Status: Invalid => Confirmed
** Changed in: tahoe-lafs (Ubuntu Natty)
Status: Confirmed => Invalid
** Changed in: pycryptopp (Ubuntu Natty)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/811721
Title:
update pycryptopp to version 0.5.29-1 in natty
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pycryptopp/+bug/811721/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
