Bruce Dubbs wrote: > > No. It just means that there was a glitch that needs to be worked out > as a part of the conversion. We won't (can't) upgrade to the new system > until all such problems are worked out.
I think I found the problem. (Btw, I was pinging the wrong bug in blfs-bugs. I thought the script had moved on to bug 1662, but it was still trying to parse 1661.) Apparently, if I'm looking at this correctly, the upgrade to Bugzilla 2.18.3 introduced a new bug of its own. (or a new feature, hard to tell) The bugzilla2trac.py script seems to be failing on new bugs that have no modification time. Look at the 'Last modified' field for bugs like this: http://blfs-bugs.linuxfromscratch.org/show_bug.cgi?id=1661 And compare that to a bug that was entered some time ago (I think before the bugzilla upgrade) but that hasn't been modified since it was opened either: http://blfs-bugs.linuxfromscratch.org/show_bug.cgi?id=1463 On 1463, the 'Last modified' field is the same as the 'Opened' field. I believe the bugzilla2trac.py script is expecting a valid time there. This is the type of error I'm getting: Traceback (most recent call last): File "bugzilla2trac.py", line 883, in ? main() File "bugzilla2trac.py", line 880, in main convert(BZ_DB, BZ_HOST, BZ_USER, BZ_PASSWORD, TRAC_ENV, TRAC_CLEAN) File "bugzilla2trac.py", line 804, in convert ticketid = trac.addTicket(**ticket) File "bugzilla2trac.py", line 341, in addTicket (id, type.encode('utf-8'), time.strftime('%s'), AttributeError: 'NoneType' object has no attribute 'strftime' So, my plan is to manually add the 'Opened' time to the 'Last modified' field in the bugs database. Any objections? -- JH -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
