Edgewall Software
Modify

Ticket #7333 (new defect)

Opened 4 years ago

Last modified 2 years ago

[PATCH] bugzilla2trac.py: import Bugzilla version 2.18.4

Reported by: thomas.klenner@… Owned by:
Priority: normal Milestone: not applicable
Component: contrib Version: 0.10.4
Severity: normal Keywords: bugzilla verify patch
Cc:
Release Notes:
API Changes:

Description

I just managed to import my bugs from Bugzilla version 2.18.4 into Trac Version 0.10.4.

However, some changes were necessary to the original Bugzilla DB contents as well as to the import script itself:

Trac needs unique product names

I used the option in the conversion script:

COMPONENTS_FROM_PRODUCTS = False

This caused the script to fail because my Bugzilla DB contained the same component name for various products.

After renaming the duplicate components, the script managed to import them.

DB schema problem

The import of attachments failed because of a wrong check for the Bugzilla version in the script (line 824):

The correct select statement from tables attachments and attach_data depends on the Bugzilla version. The script uses the table attach_data for versions greater or equal than 2180. However, this table was introduced in version 2211 (see http://www.ravenbrook.com/project/p4dti/tool/cgi/bugzilla-schema/).

After changing the condition to

        if BZ_VERSION >= 2210:

the import succeeded.

Multiple attachments.isobsolete at the same time

My bugzilla DB contained three changes of type "attachments.isobsolete" for the same bug at the same time.

This caused a duplicate primary key error in table ticket_change.

See my comments on Ticket #6753 for details.

Attachments

Change History

comment:1 Changed 4 years ago by Piotr Kuczynski <piotr.kuczynski@…>

  • Component changed from general to ticket system
  • Keywords bugzilla verify patch added; Bugzilla import removed
  • Milestone set to 0.10.6
  • Summary changed from bugzilla2trac.py: import Bugzilla version 2.18.4 to [PATCH] bugzilla2trac.py: import Bugzilla version 2.18.4

comment:2 follow-ups: Changed 4 years ago by jruigrok

  • Status changed from new to assigned

Thomas, I fixed the version comparison. Is it safe to say that this ticket can be closed since the other points are raised in other tickets?

comment:3 in reply to: ↑ 2 Changed 4 years ago by thomas.klenner@…

Replying to jruigrok:

Thomas, I fixed the version comparison. Is it safe to say that this ticket can be closed since the other points are raised in other tickets?

Yes, that's OK for me.

comment:4 Changed 4 years ago by anonymous

  • Milestone changed from 0.10.6 to 0.11.1

comment:5 in reply to: ↑ 2 Changed 3 years ago by cboos

  • Milestone changed from 0.11.2 to 0.11.3

Replying to jruigrok:

Thomas, I fixed the version comparison. Is it safe to say that this ticket can be closed since the other points are raised in other tickets?

Well apparently not, source:branches/0.11-stable/contrib/bugzilla2trac.py@6820#L824 still has the test against 2180 and not 2211 as Thomas said it should be.

comment:6 Changed 3 years ago by cboos

(the problem with the link above has been recorded as #7744)

comment:7 Changed 3 years ago by anonymous

  • Resolution set to fixed
  • Status changed from assigned to closed

comment:8 Changed 3 years ago by ebray

  • Resolution fixed deleted
  • Status changed from closed to reopened

Thank you anonymous.

comment:9 Changed 3 years ago by jruigrok

Christian, are you ok with just merging the entire version of the script in trunk to the branch?

comment:10 Changed 3 years ago by cboos

Sure, there's no difference in the ticket schema between 0.11 and trunk that justify having a different conversion script in both branches. So feel free to backport the whole thing if you want.

comment:11 Changed 3 years ago by cboos

  • Milestone changed from 0.12.1 to not applicable

comment:12 Changed 2 years ago by jruigrok

  • Owner jruigrok deleted
  • Status changed from reopened to new

comment:13 Changed 2 years ago by cboos

  • Component changed from ticket system to contrib
View

Add a comment

Modify Ticket

Change Properties
<Author field>
Action
as new
as The resolution will be set. Next status will be 'closed'
to The owner will be changed from (none). Next status will be 'new'
The owner will be changed from (none) to anonymous. Next status will be 'assigned'
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.