Edgewall Software
Modify

Opened 11 years ago

Last modified 9 years ago

#7333 new defect

[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: Branch:
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 (0)

Change History (13)

comment:1 by Piotr Kuczynski <piotr.kuczynski@…>, 11 years ago

Component: generalticket system
Keywords: bugzilla verify patch added; Bugzilla import removed
Milestone: 0.10.6
Summary: bugzilla2trac.py: import Bugzilla version 2.18.4[PATCH] bugzilla2trac.py: import Bugzilla version 2.18.4

comment:2 by Jeroen Ruigrok van der Werven, 11 years ago

Status: newassigned

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?

in reply to:  2 comment:3 by thomas.klenner@…, 11 years ago

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 by anonymous, 11 years ago

Milestone: 0.10.60.11.1

in reply to:  2 comment:5 by Christian Boos, 11 years ago

Milestone: 0.11.20.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 by Christian Boos, 11 years ago

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

comment:7 by anonymous, 10 years ago

Resolution: fixed
Status: assignedclosed

comment:8 by ebray, 10 years ago

Resolution: fixed
Status: closedreopened

Thank you anonymous.

comment:9 by Jeroen Ruigrok van der Werven, 10 years ago

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

comment:10 by Christian Boos, 10 years ago

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 by Christian Boos, 10 years ago

Milestone: 0.12.1not applicable

comment:12 by Jeroen Ruigrok van der Werven, 10 years ago

Owner: Jeroen Ruigrok van der Werven removed
Status: reopenednew

comment:13 by Christian Boos, 9 years ago

Component: ticket systemcontrib

Modify Ticket

Change Properties
Set your email in Preferences
Action
as new The ticket will remain with no owner.
The ticket will be disowned.
as The resolution will be set.
The owner will be changed from (none) to anonymous.

Add Comment


E-mail address and name can be saved in the Preferences .
 
Note: See TracTickets for help on using tickets.