On 10/16/06, Andrew <email@example.com> wrote:
> Hi, maybe someone remembers me from years ago, I worked some
> on the manual.
> I am hoping someone can help me with a Subversion database problem.
> I'm resuming development on a 40,000 line Subversioned project that
> I haven't worked on in 2.5 years. Apparently:
> (a) the last version used with this project was Subversion 0.19, and
> (b) my machine was upgraded to use Subversion 1.1.4.
> I gather that I need to do a dump/load cycle to get from database schema
> version 1 to 2, and another to get from version 2 to 3. Where can I
> get (Cygwin) Windows executables of the svnadmin command for this?
> I didn't see anything in the Windows download area here:
That's because you need to be here:
(deeper into the tree)
> P.S. I didn't see an old svnadmin executable on my machine. Maybe the
> installation process for subversion could save the old svnadmin.
Post-1.0 svnadmin's can read older repository formats, making this not
necessary. Pre-1.0, this was an explicit warning: the schema could
change at every release.
> P.P.S. It sure would be nicer if 'svnadmin dump' could deal with
> schema formats for all previous versions. Maybe this is painful to
Ofcourse this was too difficult to implement: it would mean supporting
over 6 different repository schema's currently. And: as said before:
you were warned explicitly about the dangers of using non-1.0
> P.P.S. The error messages about repositories being out of date and/or
> the SVN FAQ could be changed to include version numbers of the svnadmin
> command that can be used for the various database schema.
We have the Project status page which tells you when schema-changes
occurred. That way you can find out which versions are compatible and
which ones are not.
> P.P.P.S. I hoped that with the difference in attitude between CVS and
> Subversion that this kind of thing would not happen with Subversion.
Post-1.0 it won't. Pre-1.0 this promise wasn't tractable: Subversion
was a research project pre-1.0 meaning we were allowed to make
mistakes. Having to maintain compatibility with those mistakes would
have brought progress towards 1.0 to its knees. That what you want?
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Mon Oct 16 16:19:08 2006