Comment 1 for bug 708655

I did some initial investigation into this, and it seems that the
importer has some kind of bug when there are no existing Debian import
branches but there are existing Ubuntu import branches.

(For some reason, this is the situation for the sysvinit package.)

A completely fresh import run on my local workstation, ignoring the
existing Launchpad branches succeeded.

Therefore, if we are willing to delete the existing imported branches on
Launchpad, that would be the most expedient way to obtain a working import.

There is only one user-created branch based on the current history on
Launchpad, and that is just a one-line typo fix.

Therefore, I think this approach wouldn't be unreasonable.

To do this, we would just need someone with jubany access to run
delete_branches_from_lp.py and requeue_package.py --full for sysvinit.

An alternative solution which would *probably* also work would be to
manually branch and push the appropriate subsets of the current import
branches to Debian lenny, squeeze, wheezy and sid branches on Launchpad,
set them as official, and requeue_package.py --full.