Opened 17 years ago
Closed 5 years ago
#7333 closed defect (wontfix)
[PATCH] bugzilla2trac.py: import Bugzilla version 2.18.4
Reported by: | Owned by: | ||
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | contrib | Version: | 0.10.4 |
Severity: | normal | Keywords: | verify, patch, bugzilla2trac |
Cc: | Branch: | ||
Release Notes: | |||
API Changes: | |||
Internal 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 (15)
comment:1 by , 17 years ago
Component: | general → ticket 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 |
follow-ups: 3 5 comment:2 by , 17 years ago
Status: | new → assigned |
---|
comment:3 by , 17 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 , 16 years ago
Milestone: | 0.10.6 → 0.11.1 |
---|
comment:5 by , 16 years ago
Milestone: | 0.11.2 → 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:7 by , 16 years ago
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
comment:9 by , 16 years ago
Christian, are you ok with just merging the entire version of the script in trunk to the branch?
comment:10 by , 16 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 , 15 years ago
Milestone: | 0.12.1 → not applicable |
---|
comment:12 by , 15 years ago
Owner: | removed |
---|---|
Status: | reopened → new |
comment:13 by , 15 years ago
Component: | ticket system → contrib |
---|
comment:14 by , 5 years ago
Keywords: | bugzilla2trac added; bugzilla removed |
---|
comment:15 by , 5 years ago
Milestone: | not applicable |
---|---|
Resolution: | → wontfix |
Status: | new → closed |
bugzilla2trac.py
is no longer maintainer by Trac developers and is being deleted from the trunk. If you need the plugin, please consider copying it from 1.4-stable and creating a plugin on trac-hacks.org.
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?