Ubuntu

The Bugzilla migration on Friday went quite well, so we’ve now got all the old Ubuntu bug reports in Launchpad. Before the migration, we were up to bug #6760. Now that the migration is complete, there are more than 28000 bugs in the system. Here are some quick points to help with the transition:

• All bugzilla.ubuntu.com accounts were migrated to Launchpad accounts with a few caveats:
  1. If you already had a Launchpad account with your bugzilla email address associated with it, then the existing Launchpad account was used.
  2. No passwords were migrated from Bugzilla, due to differences in the method of storing them. You can set the password on the account at https://launchpad.net/+forgottenpassword.
  3. If you had a Launchpad account but used a different email to the one on your Bugzilla account, then you now have two Launchpad accounts. You can merge the two accounts at https://launchpad.net/people/+requestmerge.
• If you have a bugzilla.ubuntu.com bug number, you can find the corresponding Launchpad bug number with the following URL:
  

  http://launchpad.net/malone/bugtrackers/ubuntu-bugzilla/$BUGZILLA_ID

  This will redirect to the Launchpad bug watching that bugzilla bug. This URL can easily be used to make a Firefox keyword bookmark.

• You can file bugs on Ubuntu at https://launchpad.net/distros/ubuntu/+filebug. Note that the form expects a source package name rather than a binary package name. If you only have a binary package name, you can use the following command to find the source package name:
  

  apt-cache show $packagename | grep ^Source:

  We’ll make it easier to enter bugs when you only know the binary package name in the future.

• The Launchpad data model for bugs differs from Bugzilla in that a single bug can be targetted at multiple packages or products (internally, we call these bug tasks). To change information about a bug task (source package name, assignee, status, priority, severity, etc), you must first click on the bug target in the “fix requested in” table at the top of the bug page.

There are still a few issues that need to be ironed out. The mailing lists subscribed to most Ubuntu bugs are not yet properly configured to accept mail from Launchpad, so result in “held for moderation” messages. These issues should get fixed shortly.

The migration is finally going to happen, after much testing of migration code and improvements to Malone.

If all goes well, Ubuntu will be using a single bug tracker again on Friday (as opposed to the current system where bugs in main go in Bugzilla and bugs in universe go in Malone).

One of the things that was discussed at UBZ was moving Ubuntu’s bug tracking over to Launchpad. The current situation sees bugs in main being filed in bugzilla while bugs in universe go in Launchpad. Putting all the bugs in Launchpad is an improvement, since users only need to go to one system to file bugs.

I wrote the majority of the conversion script before the conference, but made a few important improvements at the conference after discussions with some of the developers. Since the bug tracking system is probably of interest to people who weren’t at the conf, I’ll outline some of the details of the conversion below:

• We are only migrating the open bugs — the existing bugzilla will remain available to read those bugs though.
• Any bugzilla user account associated with an open bug (asignee, reporter, cc, qa contact or commenter) will be imported into Launchpad. If you already have a Launchpad account but use a different email for your bugzilla account, you have the following options:
  1. Add your bugzilla email to your Launchpad account.
  2. In bugzilla, change your email to one of the addresses registered to your Launchpad account.
  3. After the migration, merge the extra account into your existing account.

  Note that passwords are not migrated, because Launchpad uses a different password hashing algorithm to Bugzilla

• All comments and attachments are imported.
• Bugs are filed against the appropriate package under the “Ubuntu” distribution in Launchpad.
• A bug watch is created, pointing at the original Bugzilla bug, so you can see any information not migrated.
• If the bug was marked UPSTREAM and a bug tracker URL is included in the bugzilla URL field, then we attempt to create a bug task against the upstream product and link it to the remote bug. This depends on the upstream product existing and being linked to the package, so doesn’t always succeed. This feature was implemented to keep Sebastien happy, 68% of the UPSTREAM bugs are assigned to him.
• Some of the bugzilla bugs are actually imported from debbugs. For these bugs, a bug task will be filed against Debian linked to the appropriate debbugs bug.

There are a few other things that need completing on the production Launchpad server before we can do the migration, but we should have a test import done on the staging server tomorrow some time.