User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:22.214.171.124) Gecko/2008120122 Firefox/3.0.5 Build Identifier: 3.2 gnatsparse was written for an ancient database schema. It no longer works with the newer schemas. The ability to migrate existing from bug tracking database plays a major role in deciding whether or not to migrate to a new bug tracking system. For this reason, I believe the inability to convert gnats data is a major impediment to adopting bugzilla. If this feature is not important enough to fix then gnatsparse should be removed. As it is now, the apparent existence of a gnats migration tool serves only to confuse people. Reproducible: Always
As gnatsparse is in the contrib folder, it does not have an active maintainer. Bugzilla does support importing via XML which is the preferred method for bug transfer as it is more universal. I am not familiar with gnats. Does it have an XML export capability? If so, I am in favor of removing the gnatsparse script if it is no longer useful.
CC'ing Daniel, who is the author of gnatsparse.
Severity: major → normal
Version: unspecified → 3.2
gnats doesn't have any sort of XML export capability. As it stands right now, bugzilla doesn't work for people wanting to switch from gnats to a more modern system. It is certainly up to the developers to decide if gnats import should be maintained, but if it isn't maintained, then you should save people some headaches and remove gnatsparse and gnats2bz from the distribution.
Daniel, can you confirm this bug? Any plan to fix it?
It's certainly true (i can't change the bug status). I have no plans to fix it though.
Though to be ohnest, i don't see why it would be a good idea to remove it. It's not difficult to update it, and removing them will just encourage people to rewrite the things from scratch, which makes no sense
WONTFIX in favor of bug 519584, where I'm in fact working on a GNATS migrator as the first migrator.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.