Modify ↓
Opened 17 years ago
Closed 17 years ago
#7091 closed defect (duplicate)
IntegrityError while creating environment
Reported by: | Owned by: | Jonas Borgström | |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | admin/console | Version: | 0.11b2 |
Severity: | normal | Keywords: | mysql |
Cc: | Branch: | ||
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description (last modified by )
I'm not sure if this is a bug in trac or just a problem with my svn repository. I'm trying to set up trac for wxWidgets using 0.11b2 and MySQL. I'm getting an error during the initenv while it is indexing the repository:
Failed to initialize environment. (1062, "Duplicate entry '38364-wxWidgets/tags/RELEASE/samples/html/about/makefile.vc-C' for key 1") Traceback (most recent call last): File "/usr/lib/python2.4/site-packages/Trac-0.11b2-py2.4.egg/trac/admin/console.py", line 562, in do_initenv repos.sync(self._resync_feedback) File "/usr/lib/python2.4/site-packages/Trac-0.11b2-py2.4.egg/trac/versioncontrol/cache.py", line 202, in sync (str(next_youngest), File "/usr/lib/python2.4/site-packages/Trac-0.11b2-py2.4.egg/trac/db/util.py", line 50, in execute return self.cursor.execute(sql_escape_percent(sql), args) File "/usr/lib/python2.4/site-packages/Trac-0.11b2-py2.4.egg/trac/db/util.py", line 50, in execute return self.cursor.execute(sql_escape_percent(sql), args) File "build/bdist.linux-i686/egg/MySQLdb/cursors.py", line 166, in execute File "build/bdist.linux-i686/egg/MySQLdb/connections.py", line 35, in defaulterrorhandler IntegrityError: (1062, "Duplicate entry '38364-wxWidgets/tags/RELEASE/samples/html/about/makefile.vc-C' for key 1")
Is there something I can do to work around this?
Attachments (0)
Change History (2)
comment:1 by , 17 years ago
Version: | → 0.11b2 |
---|
comment:2 by , 17 years ago
Component: | general → admin/console |
---|---|
Description: | modified (diff) |
Keywords: | mysql added |
Resolution: | → duplicate |
Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
See duplicate #4378 for a discussion of the problem and possible workarounds.
(the easiest workaround here is simply to not use MySqlDb).