Comment 11 for bug 792193

Hmm. A problem.

Turns out that 2.6.24-28.83 is also linked to the bogus .orig.tar.gz. This is more than slightly annoying, as resolving this just got rather less trivial.

My suggestion at this point is that we should follow the previously outlined procedure except that instead of hacking the importer to import only hardy-release, we should hack it to only import versions strictly less than 2.6.24-28.83.

Once it has done so, and pushed the resulting branches, we then cheat, doing a manual "bzr import-dsc" of the problem package revision, then we cheat some more, and use the sqlite3 command line client to insert the new bzr revision's id and testament sha into the importer's meta.db revids table.

Then we can continue importing. But, given the incredibly long time it takes, we probably want to hack the importer so that it does so in incremental batches, rather than attempting to import all the way from hardy to oneiric in one run, and losing all of the progress if it falls over again.