Modify ↓
#9577 closed defect (fixed)
[PATCH] bugzilla2trac.py converting times to seconds instead of microseconds
| Reported by: | Owned by: | ||
|---|---|---|---|
| Priority: | normal | Milestone: | 0.12.1 |
| Component: | contrib | Version: | 0.12-stable |
| Severity: | normal | Keywords: | bugzilla2trac |
| Cc: | Branch: | ||
| Release Notes: | |||
| API Changes: | |||
| Internal Changes: | |||
Description
When running the bugzilla2trac.py migration script, timestamps from the Bugzilla database are being converted to seconds instead of microseconds, this causes all of the timestamps in the new Trac install to be very close to Epoch.
System Info:
Trac 0.12 using SQLLite backend Python 2.5 Bugzilla 3.6.1 using MySQL 5.1.42 backend O/S - OpenBSD 4.7
Attachments (1)
Change History (6)
comment:1 by , 14 years ago
by , 14 years ago
| Attachment: | timestamps_in_usecs.diff added |
|---|
patch to bugzilla2trac.py to support timestamps in microseconds
comment:2 by , 14 years ago
| Summary: | bugzilla2trac.py converting times to seconds instead of microseconds → [PATCH] bugzilla2trac.py converting times to seconds instead of microseconds |
|---|
Added patch for making the timestamp units configurable
comment:4 by , 14 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Patch applied in [10009], without the configurable part, as timestamps in 0.12 are always microseconds. To import into 0.11.x, use the importer from that branch.
comment:5 by , 14 years ago
| Owner: | changed from to |
|---|
Note:
See TracTickets
for help on using tickets.
The bugzilla2trac is not actively supported by any of the current Trac developers. Would you mind taking a shot at implementing the timestamp conversion? If you could provide a patch and test it, I would integrate it.