On Tue, Sep 28, 2010 at 5:23 AM, Tech Geek <techgeek12...@gmail.com> wrote:

> I have the subversion server running on a Debian Linux machine. The
> repositories are residing on a Windows domain shared network drive on the
> network which is mapped on the Linux machine as:
> mount -t cifs //software/svn_repositories /var/lib/svn/ -o
> username=mynet/techgeek,password=******,uid=www-data,gid=subversion,iocharset=utf8
>
> All the developers/users access the repositories using TortoiseSVN client
> from Windows machine.
>
> The problem is that if the repositories were created from TortoiseSVN then
> upon accessing the repositories (For example http://svnserver/svnrepos) I
> get:
> human-readable errcode="160043": Could not open the requested SVN
> filesystem
>
> However, if I create new repositories from the Linux machine (on which
> subversion is running), then everything works fine.
>
> I noticed when creating repositories from TortoiseSVN the value in
> db/format is "4" (non-working) and while creating repositories from Linux
> the value is "3" (working).
>

This indicates that the version of SVN on the linux box, and the version of
TSVN are not the same. I don't know what the repository version numbers are
that correspond to each svn/TSVN version (and you didn't mention which
versions you have installed). Either downgrade TSVN, or upgrade SVN on the
linux machine (upgrading the linux machine is probably easiest).


> If I change the vaule from "4" to "3" for the repositories that were
> created by TortoiseSVN then I do not longer get the above error message.
>

Never manually modify anything under the repository/db directory.


> Sounds like there is some incompatibility between the subversion engine (on
> linux) and the TortoirseSVN.
>
> I would like to enable developers/users to create repositories using
> TortoiseSVN client. Do I have to live with this situation or is there a more
> elegant workaround rather than changing the value of db/format file manually
> everytime a new repository is created?
>

Cheers,
Daniel B.

Reply via email to