You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Danny Park <dp...@MIT.EDU> on 2006/11/01 18:03:41 UTC
bdb -> fsfs migration hitches: expected '3', found '5'
Hi folks,
Sorry, but google and mailing list archives don't seem to be answering
it for me... I also apologize if this ends up being a TortoiseSVN
issue--I don't think it is, but it's possible, in which case I'll go
knocking on a different door.
After migrating my repository from bdb to fsfs (which required updating
to a more recent subversion package, since the older ones couldn't
handle the >2GB revisions from the dump file), I figured all I had to do
is replace the old repository directory with the new one.. which mostly
works.. except most of my old working copies can't sync up anymore.
They give the following error:
Expected format '3' of repository; found format '5'
Here's the context:
Server: repository sits on a linux machine's file system out on the
internet. This server runs subversion 1.4.0 (r21228), a pre-compiled
debian package. (it used to be running 1.2.something, which was unable
to import my dump files with large revisions)
What works: a working copy on the same server, which access the
repository using a file:/// url. I could "svn up" and it didn't seem to
care that the repository's format had changed.
What doesn't: working copies on two windows machines (win2k and winxp),
using tortoisesvn 1.4.0 (build 7501) which is based on subversion 1.4.0.
They access the repository with an svn+ssh:// url (and I type my unix
system password into plink each time I sync/commit). An update of the
existing working copy gives the above error. Interestingly enough, when
I try to check out a fresh copy, it also gives the above error.
I wish I still had my other working copy (also svn+ssh based) on an old
linux machine to test if that worked.. but no data there..
Any pointers?
-danny
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: bdb -> fsfs migration hitches: expected '3', found '5'
Posted by Danny Park <dp...@MIT.EDU>.
Ah.. that was it, thanks! I assumed an apt-get would take care of it
all, but we had some custom-compiled (old) binaries in /usr/local/bin,
and specifically, the old svnserve binary was getting called by sshd
instead of the new one.
-danny
Ruslan Sivak wrote:
> Sounds like you have old svn binaries still being used... check what
> version of svnserve is being used, and make sure it's using the latest
> one. If you're using apache, make sure it's using the latest module as
> well.
>
> Russ
>
> Danny Park wrote:
>>
>> Hi folks,
>>
>> Sorry, but google and mailing list archives don't seem to be answering
>> it for me... I also apologize if this ends up being a TortoiseSVN
>> issue--I don't think it is, but it's possible, in which case I'll go
>> knocking on a different door.
>>
>> After migrating my repository from bdb to fsfs (which required
>> updating to a more recent subversion package, since the older ones
>> couldn't handle the >2GB revisions from the dump file), I figured all
>> I had to do is replace the old repository directory with the new one..
>> which mostly works.. except most of my old working copies can't sync
>> up anymore. They give the following error:
>>
>> Expected format '3' of repository; found format '5'
>>
>> Here's the context:
>>
>> Server: repository sits on a linux machine's file system out on the
>> internet. This server runs subversion 1.4.0 (r21228), a pre-compiled
>> debian package. (it used to be running 1.2.something, which was
>> unable to import my dump files with large revisions)
>>
>> What works: a working copy on the same server, which access the
>> repository using a file:/// url. I could "svn up" and it didn't seem
>> to care that the repository's format had changed.
>>
>> What doesn't: working copies on two windows machines (win2k and
>> winxp), using tortoisesvn 1.4.0 (build 7501) which is based on
>> subversion 1.4.0. They access the repository with an svn+ssh:// url
>> (and I type my unix system password into plink each time I
>> sync/commit). An update of the existing working copy gives the above
>> error. Interestingly enough, when I try to check out a fresh copy, it
>> also gives the above error.
>>
>> I wish I still had my other working copy (also svn+ssh based) on an
>> old linux machine to test if that worked.. but no data there..
>>
>> Any pointers?
>>
>> -danny
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
>> For additional commands, e-mail: users-help@subversion.tigris.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: bdb -> fsfs migration hitches: expected '3', found '5'
Posted by Ruslan Sivak <rs...@istandfor.com>.
Sounds like you have old svn binaries still being used... check what
version of svnserve is being used, and make sure it's using the latest
one. If you're using apache, make sure it's using the latest module as
well.
Russ
Danny Park wrote:
>
> Hi folks,
>
> Sorry, but google and mailing list archives don't seem to be answering
> it for me... I also apologize if this ends up being a TortoiseSVN
> issue--I don't think it is, but it's possible, in which case I'll go
> knocking on a different door.
>
> After migrating my repository from bdb to fsfs (which required
> updating to a more recent subversion package, since the older ones
> couldn't handle the >2GB revisions from the dump file), I figured all
> I had to do is replace the old repository directory with the new one..
> which mostly works.. except most of my old working copies can't sync
> up anymore. They give the following error:
>
> Expected format '3' of repository; found format '5'
>
> Here's the context:
>
> Server: repository sits on a linux machine's file system out on the
> internet. This server runs subversion 1.4.0 (r21228), a pre-compiled
> debian package. (it used to be running 1.2.something, which was
> unable to import my dump files with large revisions)
>
> What works: a working copy on the same server, which access the
> repository using a file:/// url. I could "svn up" and it didn't seem
> to care that the repository's format had changed.
>
> What doesn't: working copies on two windows machines (win2k and
> winxp), using tortoisesvn 1.4.0 (build 7501) which is based on
> subversion 1.4.0. They access the repository with an svn+ssh:// url
> (and I type my unix system password into plink each time I
> sync/commit). An update of the existing working copy gives the above
> error. Interestingly enough, when I try to check out a fresh copy, it
> also gives the above error.
>
> I wish I still had my other working copy (also svn+ssh based) on an
> old linux machine to test if that worked.. but no data there..
>
> Any pointers?
>
> -danny
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: bdb -> fsfs migration hitches: expected '3', found '5'
Posted by eg <eg...@gmail.com>.
Danny Park wrote:
>
.. which mostly
> works.. except most of my old working copies can't sync up anymore. They
> give the following error:
>
> Expected format '3' of repository; found format '5'
I believe this is caused when an old (pre 1.4) svn client tries to
access a repository created with 1.4. The repos format has been upgraded
to provide new compression / performance etc.
>
>
> What works: a working copy on the same server, which access the
> repository using a file:/// url. I could "svn up" and it didn't seem to
> care that the repository's format had changed.
Makes sense the server side components are 1.4.
>
> What doesn't: working copies on two windows machines (win2k and winxp),
> using tortoisesvn 1.4.0 (build 7501) which is based on subversion 1.4.0.
> They access the repository with an svn+ssh:// url (and I type my unix
> system password into plink each time I sync/commit). An update of the
> existing working copy gives the above error. Interestingly enough, when
> I try to check out a fresh copy, it also gives the above error.
Could there be a version mismatch of the tortoiseSVN?
What happens if you install and use the svn 1.4 commandline client (not
TortoiseSVN)? See:
http://subversion.tigris.org/servlets/ProjectDocumentList?folderID=91
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org