id summary reporter owner description type status priority milestone component version severity resolution keywords cc branch changelog apichanges internalchanges 7744 source:path@rev targeting a file below a copied dir may fail Christian Boos "... when the file has not been modified since the copy and `rev` predates the copy operation itself. e.g. source:/branches/0.11-stable/contrib/bugzilla2trac.py@6820#L824 leads to: {{{ No node /branches/0.11-stable/contrib/bugzilla2trac.py at revision 6820 }}} Looking at source:/branches/0.11-stable/contrib/bugzilla2trac.py (without revision spec) works, and indeed shows a revision of r6820 for this file. This is happening because at r6820, there was no branches/0.11-stable. This behavior is actually ""correct"" if ...@6820 is supposed to be a peg revision in Subversion terminology, but it's annoying nonetheless, as the TracLinks syntax doesn't allow an alternative way of specifying the revision(*) and anyway I don't think it's a good idea to expose the peg revision vs. operative revision subtleties in Trac (http://svnbook.red-bean.com/en/1.5/svn.advanced.pegrevs.html). (*) well it does, but source:/branches/0.11-stable/contrib/bugzilla2trac.py?rev=6820 has the same problem" defect new high next-major-releases version control/browser 0.11-stable minor svn newcache itamarost@…