sysvinit package import failing

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.

Assigned to ~canonical-bazaar to execute my delete_branches_from_lp.py suggestion or reject it in favour of my less destructive but more complex alternative suggestion.

I've done your first alternative.

Whilst the import was running, I diagnosed a minor bug that I had inadvertently introduced 2 weeks ago at the bzr sprint, which would have caused the resultant history to be a bit odd (the lenny and later debian revisions would have no ancestry to the etch and earlier ones)

I asked poolie to kill the running import - we will requeue it once https://code.launchpad.net/~maxb/udd/import-ordering-fix-take-2/+merge/63335 has been deployed.

That branch has now been merged (and rolled out) and I've requeued the imports.

The import failed. I ran a test locally and it succeeded. I suspect the difference to be that there are still some ~ubuntu-branches branches of sysvinit that didn't get deleted: https://code.launchpad.net/ubuntu/+source/sysvinit/+branches

In parallel to this failure, I've found and fixed a small issue that caused a slightly more convoluted revision tree that was necessary. Therefore, please:

1) Ensure lp:udd r455 is deployed.
2) Delete the remaining ~ubuntu-branches branches of sysvinit
3) ./requeue_package.py --full sysvinit

and then, fingers crossed, we should actually have a working import a few hours later.

james_w has moved the troublesome branches, so now we just need the current lp:udd deployed and a ./requeue_package.py --full sysvinit

On Fri, 10 Jun 2011 18:45:46 -0000, Max Bowsher <email address hidden> wrote:
> james_w has moved the troublesome branches, so now we just need the
> current lp:udd deployed and a ./requeue_package.py --full sysvinit

I've done that too. It's chewing on it now.

Thanks,

James

It worked - resolving bug.