Ubuntu
pycryptopp package

  1. Bug #811721
  2. Comment #9

Comment 9 for bug 811721

Revision history for this message
Clint Byrum (clint-fewbar) wrote : Re: update pycryptopp to version 0.5.29-1 in natty

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.