Launchpad itself

Request for staging import of SF bug data

Asked by Martin Gieseking

I'd like to migrate the bug tracker of my dvisvgm project from SourceForge to Launchpad. The exported data could be converted smoothly with sfbugs2launchpad, and the resulting xml file validates without errors against bug-export.rnc. Here's the link to the xml file:

http://dl.dropbox.com/u/15534106/dvisvgm-bugs.xml

Please import the bug data into the staging area. Let me know if you need further information or if any action is required on my part. Thank you very much in advance.

Question information

Language:
English Edit question
Status:
Solved
For:
Launchpad itself Edit question
Assignee:
[LEGACY] Canonical WebOps Edit question
Solved by:
Steve McInerney
Solved:
Last query:
Last reply:
Revision history for this message
Deryck Hodge (deryck) said : 		#1

I'm doing a couple sanity checks on the file locally and will then assign this question to a webops to get imported to staging for preview.

Revision history for this message
Deryck Hodge (deryck) said : 		#2

Also, just to be clear, is this the project we're importing the bugs into?

https://launchpad.net/dvisvgm

Revision history for this message
Martin Gieseking (martin-gieseking) said : 		#3

Yes, sorry for the missing information. https://launchpad.net/dvisvgm is the correct target.

Revision history for this message
Deryck Hodge (deryck) said : 		#4

Converting back to an open question and assigning to webops. We're good to go for a staging import now.

Revision history for this message
David Ames (thedac) said : 		#5

I have run the import on staging. Lets verify against https://staging.launchpad.net/dvisvgm. If that looks good I will import in production.

Revision history for this message
Martin Gieseking (martin-gieseking) said : 		#6

Thank you for importing the data into the staging area, David.
The bug descriptions and comments look fine. Some of the attached files seem to be broken, though. For instance, the patch https://bugs.staging.launchpad.net/dvisvgm/+bug/919192/+attachment/2683628/+files/gcc4.4.patch contains html stuff from SourceForge. Maybe the SF export function doesn't work properly for attachments. Since all bugs are already closed, I could live with that. However, it would be even better to keep the complete bug history with all attachments available. I'll have a look at the XML file again and try to replace the broken attachments with correct ones.

Revision history for this message
Martin Gieseking (martin-gieseking) said : 		#7

I have downloaded all attachments from SF separately and updated the "contents" elements with a small xquery script. The resulting XML file is here:
http://dl.dropbox.com/u/15534106/dvisvgm-bugs2.xml
Could you please drop the current bugs and import them again from this file?

Revision history for this message
David Ames (thedac) said : 		#8

I have re-imported the new bug file after chaniging the nicknames to dvisvgm-oldbugid.

Revision history for this message
Martin Gieseking (martin-gieseking) said : 		#9

OK, great, thank you. Everything looks good now. You can import the bug tickets into the production system.

Revision history for this message
Steve McInerney (spm) said : 		#10

sorry Martin, been a tad tied up the past few days, should be able to sort this tomorrow.

Revision history for this message
Martin Gieseking (martin-gieseking) said : 		#11

That's not a problem at all. The import is not that urgent to me. I'm nonetheless looking forward to it.

Revision history for this message
Best Steve McInerney (spm) said : 		#12

Heya Martin, bugs imported.
for the record, here's the output of the import:
http://paste.ubuntu.com/825791/ help match bug X in old, to Bug Y in new shiny.

Cheers!

Revision history for this message
Martin Gieseking (martin-gieseking) said : 		#13

Great. Thank you very much, Steve.

Revision history for this message
Martin Gieseking (martin-gieseking) said : 		#14

Thanks Steve McInerney, that solved my question.