http://qa.mandrakesoft.com/show_bug.cgi?id=5195
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution| |FIXED
------- Additional Comments From [EMAIL PROTECTED] 2003-04-09 11:26 -------
No, it will work if the repository use the old db schema, numbered 1.
If you use svnadmin 0.28 in a old repository, you will see that it requires
version 2.
This is what cause problem, according to
http://svn.collab.net/repos/svn/trunk/notes/repos_upgrade_HOWTO
they do not talk of upgrading from 0.26, or 0.27, but from all old releases.
the solution of using svnadmin-0.27 worked for me, i only had to run
"svnadmin-0.27 recover" to restore the base, because there was a problem with
libdb4 and libdb4.1.
it would be nice to have it inclued in the documentation.
http://www.contactor.se/~dast/svnusers/archive-2003-08/0416.shtml
http://www.contactor.se/~dast/svnusers/archive-2003-08/0422.shtml
Having a message in %post is bad, people using rpmdrake would not be able to
see it.
--
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.
