svn repository entries missing

[crissi99@…]

After upgrade from 0.12.3 trac-admin repository resync "*" does sync the svn repo but a lot of revisions are not found (svn has ~ 28000, found: ~ 280). Trac is running on Debian Squeeze using python2.6 (2.6.6) and python-subversion 1.6.12dfsg-6. Trac 0.12.3 does find all revisons.

[Christian Boos]

Great… but without further details, we won't be able to fix anything (if there's something to fix, even).

What is your repository path? If it's pointing to a subpath in the repository, then maybe you just have 280 revisions on that path (we call that "scoped repository").

It would be highly surprising that there could be a real bug at work here, given no one else ever had such an issue. If you really think there's a bug, consider providing us with a copy of the repository (or an ssh access to the box), by private mail.

[anonymous]

What is your repository path? If it's pointing to a subpath in the repository, then maybe you just have 280 revisions on that path (we call that "scoped repository").

I specified the path to the repository itself (not a checkout):

ls /opt/svn/myrepo -l total 48 drwxr——x 2 svnrep svnrepo 4096 1. Mar 2012 conf drwxr——x 7 svnrep svnrepo 4096 29. Sep 11:03 db -rwxrwx—- 1 svnrep svnrepo 2 1. Mar 2012 format drwxr——x 2 svnrep svnrepo 4096 1. Mar 2012 hooks drwxrwx—- 2 svnrep svnrepo 4096 1. Mar 2012 locks -rw-rw—— 1 svnrep svnrepo 229 1. Mar 2012 README.txt

[crissi99@…]

I got it working. The problem was caused by wrong encoding of fields in node_change mysql table, so the ticket can be closed but see the hint below.

Btw: the trac.log shows 2012-09-29 12:57:16,269 Trac[cache] WARNING: Revision 283 already cached: IntegrityError(1062, "Duplicate entry '5-0000000283-code/ext/sendmail.em.metad' for key 'PRIMARY'") and I think that error should be also reported to trac-admin on resync.

[Remy Blank]

Thanks for reporting back.