Request Migration of Issues from SourceForge

We are more than happy to do, but we need an export of your bugs from sourceforge that we import into Launchpad. The documentation about the format is at https://help.launchpad.net/Bugs/ImportFormat , but I couldn't find anything about how to do that from sourceforge.

Okay, I heard that you could do a direct import but I guess not. I wrote a script to build the file. What is the best way to send it over? Just attach it here?

Okay, I have posted the dump somewhere. It will be available at http://www.engsoc.org/~kevincox/d/autosizer-launchpad-import.xml until the import is done.

I've attempted to import your XML into a development instance of Launchpad, and it fails since all of the dates in the file do match the format needed, for example:

ValueError: time data '2013-10-27T11:13:22' does not match format '%Y-%m-%dT%H:%M:%SZ'

All of them need a Z appended.

Okay, I have updated the file at that link http://www.engsoc.org/~kevincox/d/autosizer-launchpad-import.xml. Hopefully everything goes smoothly

I have successfully imported your bugs into the autosizer project I've created on one of our staging instances -- https://bugs.qastaging.launchpad.net/autosizer . The bugs each have a nickname, autosizer-<number>, which corresponds to the id of the bug in the XML file, for example https://bugs.qastaging.launchpad.net/bugs/autosizer-8 .

Please check the imported bugs carefully and let me if there are any problems.

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 05/11/13 23:51, Steve Kowalik wrote:
>
> Please check the imported bugs carefully and let me if there are
> any problems.
>

Oops, I didn't notice the note that the first comment was considered the
description. I have updated the dump. Other than that everything
looked good.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iF4EAREIAAYFAlJ6fE0ACgkQwHWKOzTVLnQ/6wD7BXgQanAKrWQvfeYifX5bckfh
HH7Md1XQYmiDBj9isDYA/ApGGJZwEbM4B2e9Oy7cYc85qYwsrokNr+U54LL/KG8G
=XEPA
-----END PGP SIGNATURE-----

I have successfully imported your bugs into the autosizer project I've created on our other staging instance -- https://bugs.staging.launchpad.net/autosizer . As before, the bugs have nicknames, and should match up with the same bug nicknames on qastaging.

Please check the imported bugs carefully, and also be advised that staging (but not qastaging) will reset its database every weekend.

Sorry but I messed it up again. All of the data looked good in that import but the attachments didn't download, instead redirecting to a login page that got downloaded.

I have updated the dump again.

I have created a new project on qastaging to import your bugs into -- https://bugs.qastaging.launchpad.net/autosizer2 . The nicknames for the bugs has also changed to autosizer2, since they must be unique.

As before, please check the imported bugs carefully.

Thanks Steve,

I have checked over the imported bugs and they look perfect.

Thanks Steve, It all looks great.

Thanks Steve Kowalik, that solved my question.