http://qa.mandrakesoft.com/show_bug.cgi?id=5195
------- Additional Comments From [EMAIL PROTECTED] 2003-05-09 06:10 ------- On Thu, Sep 04, 2003 at 11:26:08AM +0200, [scherer.michael] wrote: I was talking about the sever/client interoperability. For that they as a matter of policy only guarantee compatability between one major revision back (e.g. .27 will be compatable with .26 but .28 will not necessarily be guaranteed). You can find their policy at: http://subversion.tigris.org/project_faq.html#interop I was thinking this applied to the schema format but apparently they don't apply it to that. However, because of this policy and subversions instability we should encourage people to do dump/load at upgrade time everytime. This is all the better reason to urge people to use svnadmin dump *BEFORE* upgrading. Always doing a svnadmin dump before an upgrade and a svnadmin load after, will always avoid issues like this. My point is including an old svnadmin is only a solution for this particular issue. Doing the dump before an upgrade and a load after is the only reliable way to ensure a good clean upgrade. It's unreasonable to carry around dozens of old svnadmin versions to help people upgrading to deal with specific issues... IMHO the 0.27 svnadmin should be removed from the package. I understand it helped you get out of a sticky situation, but having it implies that we'll provide that sort of thing in the future. The problem is they can choose to change the schema anytime they want. Do we carry a svnadmin version for every schema version? I didn't intend it to be the only message. Just an extra notice... I figure most people using subversion as a server are likely to be using urpmi not rpmdrake... -- 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: RESOLVED 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.
