svn-v4 revids are used for tags on an svn-v3 branch

Bug #322856 reported by Matt Nordhoff
4
Affects Status Importance Assigned to Milestone
Bazaar Subversion Plugin
Fix Released
Medium
Jelmer Vernooij

Bug Description

Latest bzr.dev, bzr-svn 0.5 branch, subvertpy trunk as of ~today.

svn://svn.lighttpd.net/lighttpd/branches/lighttpd-1.4.x
svn://svn.lighttpd.net/lighttpd/trunk

The above two branches use svn-v3 revision IDs (except for some normal bzr IDs, and the latest revision being svn-v4), but bzr-svn makes some/most/all of the tags use svn-v4 IDs, meaning "bzr tags" displays their revnos as "?" and they point to nonexistent revisions, making them completely useless. [Woah, run-on sentence.]

I pastebinned an example a week ago: http://paste.pocoo.org/show/BIEg11uNyMGQ4Fr1phem/

The number of svn-v4 IDs has gone up over time. First it was like 15-20%, then like 75%, and now there are only a couple svn-v3 IDs left. I have a habit of deleting and recreating my svn-cache and the repo itself, so maybe it has to do with that?

(I haven't created any clean branches to help debug this. My branches should be clean enough, and I've abused their svn server enough lately... More importantly, it's melting my brain.)

Jelmer Vernooij (jelmer)
Changed in bzr-svn:
assignee: nobody → jelmer
importance: Undecided → Medium
status: New → Triaged
Jelmer Vernooij (jelmer)
Changed in bzr-svn:
milestone: none → 0.5.0
Jelmer Vernooij (jelmer)
Changed in bzr-svn:
status: Triaged → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.