You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Art Haas <ah...@airmail.net> on 2003/06/28 00:18:48 UTC
Problem with checking out a repository
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
--
Man once surrendering his reason, has no remaining guard against absurdities
the most monstrous, and like a ship without rudder, is the sport of every wind.
-Thomas Jefferson to James Smith, 1822
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Problem with checking out a repository
Posted by kf...@collab.net.
Ben Collins-Sussman <su...@collab.net> writes:
> Hey Michael Price... it might be good to "remind" people of our
> compatibility policy when you send out release announcements.
>
> ("Here is svn 0.25; it will only interoperate with 0.24 or 0.25
> clients and servers.")
Hmmm, let's be careful with this. Note that our policy is not:
"Subversion clients and servers shall not work when there's more
than one minor revision of difference."
but rather:
"They *will* work when there is no greater than one minor revision
difference."
IOW, we're not required (nor even expected) to break compatibility
with older releases, unless there's a good reason. So let's instead
say something like:
Here is svn 0.25. A 0.25 server will interoperate with a 0.24
client, and a 0.24 server with a 0.25 client. We [do|don't] know
of the following incompatibilities with older revisions: ...
-K
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Problem with checking out a repository
Posted by Ben Collins-Sussman <su...@collab.net>.
cmpilato@collab.net writes:
> Pre-1.0, our stated compatibility promise is that a server and client
> that are no younger than one minor revision apart will work together.
Hey Michael Price... it might be good to "remind" people of our
compatibility policy when you send out release announcements.
("Here is svn 0.25; it will only interoperate with 0.24 or 0.25
clients and servers.")
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Problem with checking out a repository
Posted by Art Haas <ah...@airmail.net>.
On Fri, Jun 27, 2003 at 10:40:43PM -0500, cmpilato@collab.net wrote:
> Ross Mark <ro...@controllingedge.com.au> writes:
>
> > 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.
>
> Pre-1.0, our stated compatibility promise is that a server and client
> that are no younger than one minor revision apart will work together.
>
> So, a 0.24 client will work with a 0.23, 0.24, or 0.25 server. A 0.20
> server will work with a 0.19, 0.20, or 0.21 client. Outside that, all
> bets are off. Once we approach 1.0 though, we won't be expecting
> everyone to keep up with bleeding edge like this any more.
OK, thanks for the info. I'll look to see how soon I can upgrade the
subversion binary on the remote machine.
Subversion has been working wonderfully for my needs so far, so my thanks
go to all the developers. It's nice to see now that the Linux Kernel is
accessible too, and I've downloaded the 2.4 tree just to see subversion
in action on such a large repository. Needless to say it has handled the
2.4 kernel tree without difficulty. Nice.
Art Haas
--
Man once surrendering his reason, has no remaining guard against absurdities
the most monstrous, and like a ship without rudder, is the sport of every wind.
-Thomas Jefferson to James Smith, 1822
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Problem with checking out a repository
Posted by cm...@collab.net.
Ross Mark <ro...@controllingedge.com.au> writes:
> 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.
Pre-1.0, our stated compatibility promise is that a server and client
that are no younger than one minor revision apart will work together.
So, a 0.24 client will work with a 0.23, 0.24, or 0.25 server. A 0.20
server will work with a 0.19, 0.20, or 0.21 client. Outside that, all
bets are off. Once we approach 1.0 though, we won't be expecting
everyone to keep up with bleeding edge like this any more.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Problem with checking out a repository
Posted by Ross Mark <ro...@controllingedge.com.au>.
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