Comment 1 for bug 899286

Hey Michael -

This actually sounds like a more or less standard backport request. Tweaking the package to deal with toolchain changes is completely acceptable - we have to do it with some regularity.

However, in order to make sure the non-LTS upgrade path is still safe, we would also need to backport apt-clone to maverick, natty, and oneiric. I'll go ahead and open bug tasks. Maverick should have dh_python2, so I'm assuming that no source changes will be required for any of those.

It also looks like apt-clone has 1 reverse-dependency and 1 reverse-build-dependency in both natty and oneiric:

apt-clone
---------
* ubiquity
  [ ] natty (Reverse-Depends)
  [ ] oneiric (Reverse-Depends)
* update-manager
  [ ] natty (Reverse-Build-Depends)
  [ ] oneiric (Reverse-Build-Depends)

As far as I can tell, using ubiquity outside of the live CD environment doesn't make any sense, so I don't think we need to enforce testing that one, so that just leaves update-manager.

So that makes this a more or less standard backport, and we just have a few things that need to be tested:

 - Please make sure that the package builds/installs/runs without modification on maverick/natty/oneiric (I'm assuming you've already tested lucid)
 - Please make sure that natty and oneiric's update-manager still works with the backported apt-clone.

The backports team will do a final once-over after the testing is done, so please change the status of the bug tasks to Confirmed when you've done the testing, and we'll take another look.

Thanks