See http://viewvc.tigris.org/issues/show_bug.cgi?id=265 for the original "find"
of this problem.
I'll replicate my latest response to that issue here:
--
This is a bug all the way down in the Subversion Python bindings. :-(
repos.ChangeCollector's callback interface needs to pass the 'path' of deleted
items so callback implementors know what path was actually deleted. As it
stands now, they have only 'base_path' to look at, which, while useful for
finding the last non-deleted version of the now-deleted thing in repository, is
not guaranteed to be the same path that was deleted.
--
This is a bug of my own making, an oversight when I added that callback
mechanism. Not sure how to solve the problem compatibly, short of revving the
ChangeCollector.
There is workaround, though, which is to fall back to using the not-streamy
.get_changes() function.
Bug
Major