[Bug 834361] Re: Please backport tahoe-lafs (1.8.3-0ubuntu1) from oneiric

[Evan Broder]

Thanks for the feedback, everyone. Let's look at the missing
dependencies one at a time.

> simplejson >= 1.4

It looks like the Debian maintainer at some point bumped the simplejson
dependency from (>= 1.4) to (>= 2.1.1). Zooko (or anyone), do you have
any idea why the dependency might have gotten bumped so much higher than
tahoe-lafs requires? If that dependency is artificially high, then
relaxing it back to (>= 1.4) would greatly simplify the backport.
However, if 2.1.1 or higher is actually required, that will require a
very invasive backport - simplejson has several dozen reverse
dependencies that would need to be tested.

> foolscap >= 0.6.1

A new enough version of foolscap was first made available in Natty.
Before we can proceed with the tahoe-lafs backport, we will need to
backport foolscap. Can someone please open a separate bug for that?

If you have either a Precise machine or an ubuntu-dev-tools daily build
installed (https://launchpad.net/~udt-developers/+archive/daily), I
recommend using the requestbackport script, which will determine all of
the testing that needs to be done for the backport.

> pycryptopp >= 0.5.20

Again, there seems to be a disagreement in the packaging. The package
depends on python-pycryptopp (>= 0.5.29) - any thoughts on why the
dependency is higher?

In any case, it looks like Natty picked up 0.5.29 by virtue of a
security update (bug #811721). I'm going to see about doing the same for
Lucid and Maverick. Fixing this through a security update or SRU would
be sufficient to move the backport forward.

-- 
You received this bug notification because you are a member of Ubuntu
Backporters, which is the registrant for natty-backports.
https://bugs.launchpad.net/bugs/834361

Title:
  Please backport tahoe-lafs (1.8.3-0ubuntu1) from oneiric

To manage notifications about this bug go to:
https://bugs.launchpad.net/lucid-backports/+bug/834361/+subscriptions