Launchpad itself

Import old Midori bugs into launchpad

Asked by Cris Dywan

Recently Midori has switched to using Launchpad for bug tracking. Before Flyspray was used, and we'd like the old bugs to be imported.

http://pyit.de/import.xml.gz

Thanks in advance.

Question information

Language:
English Edit question
Status:
Expired
For:
Launchpad itself Edit question
Assignee:
[LEGACY] Canonical WebOps Edit question
Last query:
Last reply:
Whiteboard:
Use the tested version that provides bug nick names at scp devpad:/home/curtis/midori-bug-import.xml I imported using scripts/bug-import.py --product midori midori-bug-import.xml 2>&1 | tee import.log
Revision history for this message
Curtis Hovey (sinzui) said : 		#1

I have tried a test import. In general, the information looks good. I am concerned about 436 UNKNOWN status bugs. The are difficult to find in Lp because of bug 44238.

Is there a better status that they can be mapped to? Here are some examples that have UNKNOWN status:
    http://www.twotoasts.de/bugs/index.php?do=details&task_id=3
    http://www.twotoasts.de/bugs/index.php?do=details&task_id=4
    http://www.twotoasts.de/bugs/index.php?do=details&task_id=24

Most are CLOSED like in 4 and 24. Many projects mark these bugs are INVALID or OPINION. Reading the comments of some of these, many were closed because they are duplicates. I could hack the data to make them all closed, but bug 3 looks like a problem. I do not know how many bugs have PATCH status, but I think we want them to be TRIAGED. I cannot see any information in the xml that tell me that the attachment happens to be PATCH. I could *assume* all UNKNOWN status with attachments are PATCH thus become TRIAGED if you think that is reliable test.

Revision history for this message
Cris Dywan (kalikiana) said : 		#2

Here is an updated file, with unknown states fixed: http://pyit.de/import2.xml.gz

Revision history for this message
Curtis Hovey (sinzui) said : 		#3

This data looks good. I have made a small modification that adds nick names to your data, so that search for bug midori-12 will find bug 12 from the old bug tracker.

I have asked an admin to load my version (devpad:/home/curtis/midori-bug-import.xml) into https://bugs.staging.launchpad.net/midori so that you can review the changes. If you like them, an admin will then import the bugs in <https://.bugs.launchpad.net>.

Revision history for this message
Curtis Hovey (sinzui) said : 		#4

We imported the data at https://bugs.staging.launchpad.net/midori for your review. We could not import the bug with id #886. It looks like the user is registered for Ubuntu SSO, but is not an lp user. This is a known bug.

We could run this import in production if you wish. The one bug will not be imported. I am not sure the user is legitimate. SSO may have gotten the email address from an import, it was never activated.
    <reporter name="dufeu" <email address hidden>">Guy</reporter>
Maybe we should hack the data to provide an email address and user name of an existing user, then update the bug to explain why.

Revision history for this message
Данило Шеган (danilo) said : 		#5

Christian, any news on this? Is this issue settled or is some action still required?

Revision history for this message
Данило Шеган (danilo) said : 		#6

No response for almost a month, expiring now. Please re-open if you still need some action taken.