I hit the exact same problem. I installed the 0.24.2 client on a new box
and could not check out anything from my server which was 0.20.0.
Upgrading the server to 0.24.2 fixed the problem. The 0.23 clients
worked happily against the old version. It is also weird that with the
0.24.2 client that there were no error message just an empty working
directory (with the .svn dir).
I had been avoiding upgrading the server due to possible down time and
given we were in the middle of a major product release unnecessary
changes did not seem like a good idea.
Ross
Art Haas wrote:
>Hi.
>
>I'm the developer of PythonCAD and I've been making a copy of my
>Subversion repository available at the following URL:
>
>http://subversion.pythoncad.org:9000/svn/pythoncad/trunk
>
>I heard today from someone who could not check out files from the repo,
>and I'm finding that I can't do it as well. But, I can connect to the
>repository and list the files without problem, so the repo is accessible
>over the internet ...
>
>$ svn ls http://subversion.pythoncad.org:9000/svn/pythoncad/trunk
>COPYING
>Generic/
>INSTALL
>Interface/
>MANIFEST.in
>NEWS
>README
>Tests/
>debian/
>gtkpycad.py
>prefs.py
>pythoncad.xsd
>setup.py
>www/
>$
>
>When trying to check out the repository subversion connects to the
>remote repository and reports that the checkout gets the latest
>revision, but nothing actually makes it to my machine here ...
>
>$ svn checkout http://subversion.pythoncad.org:9000/svn/pythoncad/trunk pycad_checkout
>Checked out revision 570.
>$ cd pycad_checkout
>$ ls -a
>. .. .svn
>$
>
>There should have been lots of printout indicating the files were being
>copied to my new pycad_checkout directory.
>
>Several months ago I checked the remote repository out and have been
>running 'svn update' from within that checked out directory without any
>problem. My local changes get sent to the remote repo, and 'svn update'
>brings them back. This setup was my way of checking that the changes had
>made it to the remote repo and that people could get them.
>
>I'm locally running an svn binary at 0.24.2+ (built on June 19), the
>remote repo is several revisions older - I don't recall which one but it
>wouldn't surprise me if it was a 0.1X release. I'm suspecting that the
>problem is due to the old release on the remote machine talking to the
>new release on my machine. I no longer have an older release to try the
>checkout with.
>
>If someone has an older release would they mind trying to check out the
>repo? After a bit of Googling I didn't hit any links that gave clues
>about problems checkout out repositories with different versions of
>subversion so I'm sending this.
>
>Upgrading the remote machine's subverion binaries is something I want to
>see done, but as the machine is a friends I can't just do it at my own
>choosing.
>
>Thanks in advance for any clues/suggestions/remedies.
>
>Art Haas
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Jun 28 04:20:10 2003