thearthur, typically we don't update to new upstream versions unless
they are *purely* bug fix releases. It sounds to me like this might
change the API of pycryptopp, which is unacceptable as a Stable Release
Update (https://wiki.ubuntu.com/StableReleaseUpdates). If, however, you
can show that it doesn't change the API, it can be considered.
If tahoe-lafs doesn't work with this version of the API, then it should
be patched, but not the other way around.
I'm marking the main bug task as Fix Released for both products, since
this is no longer an issue as of Oneiric. Marking Natty as Confirmed for
tahoe-lafs, but Invalid for pycryptopp since as far as I can tell this
isn't a bug in it, but rather a bug in something using its API. If I
have misunderstood or misstated the problem, please feel free to change
the status back to Confirmed and state the reasons.
** Also affects: pycryptopp (Ubuntu Natty)
Importance: Undecided
Status: New
** Also affects: tahoe-lafs (Ubuntu Natty)
Importance: Undecided
Status: New
** Changed in: pycryptopp (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: tahoe-lafs (Ubuntu)
Status: Confirmed => Invalid
** Changed in: pycryptopp (Ubuntu Natty)
Status: New => Invalid
** Changed in: tahoe-lafs (Ubuntu Natty)
Status: New => Confirmed
--
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
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
