John Williams wrote:
Hello,
We are seeing a "No changeset X in repository" error using latest Trac
(from subversion head) and subversion v1.3
The problem arises if repository_dir points to a "virtual" repository
that contains a directory that was copied from somewhere "outside" this
virtual repository.
Hard to explain, easy to demonstrate - attached recipe gives minimal
reproduceable test case.
Thanks! I tried it. There are indeed a few issues remaining with this.
I've just fixed the most annoying one (r2865), which prevented you
to look at /changeset/5, in your example.
There's still the issue of the TracBrowser.
Last September, someone reported the same error:
http://lists.edgewall.com/archive/trac/2005-September/004901.html
The resulting discussion pointed to ticket #2044 but it looks like that
was a bit off the mark. #2044 was more to do with identifying need for
resync after changing repository_dir. resync has no effect on our error.
Actually, the relevant ticket for this is #1830 (Repo susbsets have to be
fully contained, see http://projects.edgewall.com/trac/ticket/1830).
As a workaround we can avoid these virtual subrepos, but they are a nice
feature for having per-project Tracs.
I'm planning to add support for multiple directories soon, but that
won't help
for the problem reported, it will even make it more likely to occur, I
think.
I wonder if SubversionRepository.get_node should return None
rather than raising a TracError exception, when the node falls
outside of the scope of the repository restriction...
-- Christian
_______________________________________________
Trac mailing list
[email protected]
http://lists.edgewall.com/mailman/listinfo/trac
