Request for import of SABnzbd bugs

Asked by shypike on 2010-03-21

The SABnzbd project has just moved from Assembla.com to Launchpad.
Can you import our existing Trac bugs?
I have converted the Trac database to your XML import format.
All milestones used are registered on Launchpad.
Location of XML file: http://www.assembla.com/spaces/SABnzbd/documents/dgSrNwnnCr35yZeJe5afGb/download/sabnzbd.xml

We are already entering new bugs in Launchpad, I hope that is not a problem.

Thank you.

Question information

Language:
English Edit question
Status:
Solved
For:
Launchpad itself Edit question
Assignee:
No assignee Edit question
Solved by:
shypike
Solved:
2010-05-30
Last query:
2010-05-30
Last reply:
2010-05-12
Launchpad Janitor (janitor) said : #1

This question was expired because it remained in the 'Open' state without activity for the last 15 days.

shypike (shypike) said : #2

Expired because nobody answered. Great system guys!

Deryck Hodge (deryck) said : #3

I know it's frustrating that questions expire, but it does help call our attention to questions needing action. Also, we have had an enormous amount of bug imports to do lately. We have to do them in addition to other development work and they are slow to do, requiring lots of back and forth between users requesting the import and lp devs.

I have, however, just tried a local import of your xml bugs dump. I get the following error:

AssertionError: Root element is wrong: launchpad-bugs

The file needs to be formatted according to the spec at: https://help.launchpad.net/Bugs/ImportFormat

I believe the missing xmlns attr is the problem. Once the data is updated, I can try again.

Thanks! Cheers,
deryck

Graham Binns (gmb) said : #4

On 8 April 2010 16:50, Deryck Hodge
<email address hidden> wrote:
> Question #105064 on Launchpad Bugs changed:
> https://answers.edge.launchpad.net/malone/+question/105064
>
>    Status: Open => Needs information
>
> Deryck Hodge requested for more information:
> I know it's frustrating that questions expire, but it does help call our
> attention to questions needing action.  Also, we have had an enormous
> amount of bug imports to do lately.  We have to do them in addition to
> other development work and they are slow to do, requiring lots of back
> and forth between users requesting the import and lp devs.
>
> I have, however, just tried a local import of your xml bugs dump.  I get
> the following error:
>
> AssertionError: Root element is wrong: launchpad-bugs
>
> The file needs to be formatted according to the spec at:
> https://help.launchpad.net/Bugs/ImportFormat
>
> I believe the missing xmlns attr is the problem.  Once the data is
> updated, I can try again.

The missing namespace is due to bug 408935; I'll try to get a fix for
it landed tomorrow.

shypike (shypike) said : #5

Sorry didn't mean to be rude!
I used the trac-launchpad-migrator.
The tool doesn't even try to add the xlmns attribute, so it can never have produced proper output.
Fortunately, the fix was rather trivial.
I have uploaded the new file: https://www.assembla.com/spaces/SABnzbd/documents/dgSrNwnnCr35yZeJe5afGb/download/sabnzbd.xml

shypike (shypike) said : #6

Sent Graham Binns a merge proposal with the modified trac-launchpad-migrator version that I used.

Deryck Hodge (deryck) said : #7

First, thanks for the branch to fix this! There are still some issues with the format the migrator is producing. Graham is looking into it and will let us know when it's ready to go again.

Cheers,
deryck

shypike (shypike) said : #8

Graham pointed out a typo in the script which creates the wrong attribute (xlmns instead of xmlns).
I have uploaded a new file:)

It would be great if there was something to validate the import file.

Greetings
Shy

shypike (shypike) said : #9

Any chance of getting this done guys?

Deryck Hodge (deryck) said : #10

The local import worked fine. I'll get a test import into our staging server today and ping back later for you to review those bugs.

Cheers,
deryck

Deryck Hodge (deryck) said : #11

Staging import is available for review here:

https://bugs.staging.launchpad.net/sabnzbd

If these bugs look good, let me know and I'll have them imported to production Launchpad.

Cheers,
deryck

shypike (shypike) said : #12

As far as I can tell only 15 defects have been imported (of the roughly 400).
I see only 32 defects (17 existing ones).

BTW: I've uploaded a new file (removed lots of old solved defects, let's not pollute the database too much).
https://www.assembla.com/spaces/SABnzbd/documents/dgSrNwnnCr35yZeJe5afGb/download/sabnzbd.xml
It now contains 116 defects.

Deryck Hodge (deryck) said : #13

ok, let me dig into what went wrong. I'll respond when I have more info.

Cheers,
deryck

Deryck Hodge (deryck) said : #14

Just an update --

We cannot work on bug imports this week due to limited sys admin availability with the coming Ubuntu release. We will take up bug imports again next week, with the hopes of finishing off all the pending bug import questions as soon as possible.

Cheers,
deryck

Launchpad Janitor (janitor) said : #15

This question was expired because it remained in the 'Open' state without activity for the last 15 days.

shypike (shypike) said : #16

Re-activating.

Graham Binns (gmb) said : #17

Hi,

I'll try to do another import to staging for you today. Is the file above up-to-date?

shypike (shypike) said : #18

Yes, it is.

Graham Binns (gmb) said : #19

Excellent; I'll try to get to that for you today.

Graham Binns (gmb) said : #20

Whoops; meant to mark that "open"

Graham Binns (gmb) said : #21

We haven't been able to get to this today due to sysadmin availability; It's top of my list for Monday morning though, so I'll get it on staging for you then.

Graham Binns (gmb) said : #22

These bugs have now been imported into staging. Please check them over and let me know if there are any problems. If not, we'll proceed with the import to production.

shypike (shypike) said : #23

I am so sorry.
I must have missed the email and I also forgot to check this page for some time.
The content is now gone from staging.
Is it possible to do it again?

shypike (shypike) said : #24

Never mind, I now withdraw my request.
We'll figure out something else.