http://qa.mandrakesoft.com/show_bug.cgi?id=5195
------- Additional Comments From [EMAIL PROTECTED] 2003-03-09 23:50 ------- On Wed, Sep 03, 2003 at 06:16:30PM +0200, [oden.eriksson] wrote: Only if his repository is from 0.26 or 0.27... The official policy is to drop backwards support one release after. This means that if they have to make a change in 0.26 that would break backwards compatability they will keep a compatability layer in 0.26 to ease migration and drop it in 0.27. So if you're upgrading subversion more than a single release version you *MUST* dump your repos before upgrading and then load them after. Putting one version back of svnadmin may help some, but only if we haven't missed more than 1 release. IMHO, it's better to train people to always do the dump before they upgrade rather than relaying on a compatable svnadmin to be in the package... Because the later still may not be old enough to deal with their issue. Doing a dump before upgrading will always work correctly. I think the best thing to do is to put something in the package description and print something in %%post to remind them to dump before upgrading in the future... Because of the unstable nature of the db format in subversion I'm not sure what more we can do that is reliable... -- Configure bugmail: http://qa.mandrakesoft.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is. ------- Reminder: ------- assigned_to: [EMAIL PROTECTED] status: ASSIGNED creation_date: description: since subversion 0.28, svn is not able to use a repository created with the old subversion. http://svn.collab.net/repos/svn/trunk/notes/repos_upgrade_HOWTO can a old binary be provided to ease the upgrade, and the conversion after the upgrade ? only svnadmin should be ( statically ? ) build, maybe in a separated package, to not overload the current rpm.
