On 6/23/2010 7:08 PM, tsuraan wrote:
In the source browser for the new trac 0.12, I'm having a really
strange issue: in one of my repos, commits are frequently setting the
age/revision statistic of file and directories that were not a part of
the commit. It's not just a few files and directories, it's nearly
every file and directory in the entire source tree that gets its
revision changed to the latest one. svn info still gives me the
correct "Last Changed Rev" for the affected files and directories, so
I have no idea how trac is getting its wrong information for these
files. I've done trac-admin repository resync to rebuild the cached
data, and I still get the same bad revisions and change dates. I'm
using the trac-admin changeset notification right now, but it was
happening when I still had the per-page-update stuff running.
The one thing about this repo that's strange is that its trunk was svn
mv'd from a branch of a different project. We use the normal
multi-project svn setup, where the root of svn is a bunch of projects,
and under each project dir we have trunk, branches, tags. We made
this new project by svn mkdir'ing the project base, svn mv'ing the
branch into the project trunk, and then making the branch and tag
dirs. I know that's broken our ability to view changes from before
the move, so maybe it's also somehow breaking the revision/age info in
the viewer? That doesn't seem like it should be related, but I really
don't know what is going on.
If I can provide any other info that might be helpful, I'd be happy
to. It's pretty annoying having the Rev and Age columns of the source
browser being broken.
This sounds a lot like http://trac.edgewall.org/ticket/3470 can you have
a look?
-- Christian
--
You received this message because you are subscribed to the Google Groups "Trac
Users" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/trac-users?hl=en.
