"svn: No such revision '1'" error during checkout

[Monks, Peter]

G'day everyone,

I just created a new repository on our trusty SVN 1.0.5 server, and
attempted to check it out using TortoiseSVN 1.2.0 as well as the SVN
1.2.0 command line client and in both cases I get the following error
message:

svn: No such revision '1'

All of the following commands give this error:

svn checkout svn://fu.bar.com/path/to/repos
svn checkout svn://fu.bar.com/path/to/repos/
svn checkout -r HEAD svn://fu.bar.com/path/to/repos/
svn checkout -r {2005-06-20} svn://fu.bar.com/path/to/repos/

When I tried checking out the BASE revision, the error message changed
to:

svn: Bogus revision information given

Did I muck something up or is this an incompatibility between 1.2
clients and a 1.0 server?

Environment:
Server: SVN 1.0.5 from sunfreeware.com running on SPARC Solaris 5.9
Client 1: TortoiseSVN 1.2.0 build 3602 from tigris.org running on
Windows 2000
Client 2: SVN 1.2.0 from tigris.org running on Windows 2000

Thanks in advance!
Peter

----------------------------------------------------------------------
Peter Monks http://www.sydneyclimbing.com/
***@sydneyclimbing.com http://www.geocities.com/yosemite/4455/
----------------------------------------------------------------------

[Olivier Sannier]

I think you need to do at least one commit before actually doing a checkout.

[Mark Parker]

Post by Olivier Sannier
I think you need to do at least one commit before actually doing a checkout.

No, definately not.


***@kilroy D:\1
$ svnadmin create repo

***@kilroy D:\1
$ svn co file:///d:/1/repo wc
Checked out revision 0.

***@kilroy D:\1
$ svn info wc
Path: wc
URL: file:///d:/1/repo
Repository UUID: 3b81499e-e342-dd42-979c-4cc294580faf
Revision: 0
Node Kind: directory
Schedule: normal
Last Changed Rev: 0
Last Changed Date: 2005-06-20 12:29:02 -0600 (Mon, 20 Jun 2005)


***@kilroy D:\1
$

[Frank Gruman]

Strange - I always got an error on my repository when first creating it
too. The way I get around it (and it made sense to me) was that you
can't do a checkout of 'null' (i.e. there is nothing in the repository
to check out. So revision 1 is always my initial import.

Now - if what Mark says is right, then maybe there's a little loopy hole
somwhere to close. But it makes sense to me that revision 0 of a
repository just might throw errors. My advice - add some files to the
repository and see what happens at revision 1.

Regards,
Frank

Post by Mark Parker

Post by Olivier Sannier
I think you need to do at least one commit before actually doing a checkout.

No, definately not.
$ svnadmin create repo
$ svn co file:///d:/1/repo wc
Checked out revision 0.
$ svn info wc
Path: wc
URL: file:///d:/1/repo
Repository UUID: 3b81499e-e342-dd42-979c-4cc294580faf
Revision: 0
Node Kind: directory
Schedule: normal
Last Changed Rev: 0
Last Changed Date: 2005-06-20 12:29:02 -0600 (Mon, 20 Jun 2005)
$
---------------------------------------------------------------------

...

[Monks, Peter]

G'day Olivier,

How do I commit something if I haven't managed to checkout the
repository yet?

Let's pretend for a moment that I don't have access to the server, and
hence can't use the 1.0.5 client there to do the initial checkout /
dummy checkin.

Cheers,
Peter

----------------------------------------------------------------------
Peter Monks http://www.sydneyclimbing.com/
***@sydneyclimbing.com http://www.geocities.com/yosemite/4455/
----------------------------------------------------------------------

-----Original Message-----
Sent: Monday, June 20, 2005 11:12am
Subject: Re: "svn: No such revision '1'" error during checkout
I think you need to do at least one commit before actually
doing a checkout.
---------------------------------------------------------------------

[Olivier Sannier]

Post by Monks, Peter
G'day Olivier,
How do I commit something if I haven't managed to checkout the
repository yet?
Let's pretend for a moment that I don't have access to the server, and
hence can't use the 1.0.5 client there to do the initial checkout /
dummy checkin.
Cheers,
Peter

Well, that's always puzzled me as well. I've seen this been indicated as
solution in the list's archive, and just repeated it. I never had the
problem though so I cannot help you much there.
Sorry about that.

[Monks, Peter]

G'day Mark,

I'm not sure I understand what your example is demonstrating. I'm
accessing a 1.0.5 server from a 1.2.0 client over the svn:// protocol.
AFAICT you're using the same (unknown) version of SVN for both the
client and the server and using the file:// protocol - something that
is quite different and hence quite possibly doesn't exhibit the
behaviour that I'm seeing. What Olivier described is a workaround
to the problem I'm seeing, albeit one that requires that I access the
repository using something other than a remote 1.2.0 client.

Perhaps you could explain your example in a bit more detail?

Thanks!
Peter

----------------------------------------------------------------------
Peter Monks http://www.sydneyclimbing.com/
***@sydneyclimbing.com http://www.geocities.com/yosemite/4455/
----------------------------------------------------------------------

-----Original Message-----
Sent: Monday, June 20, 2005 11:33am
To: Olivier Sannier
Subject: Re: "svn: No such revision '1'" error during checkout

Post by Olivier Sannier
I think you need to do at least one commit before actually doing a
checkout.

No, definately not.
$ svnadmin create repo
$ svn co file:///d:/1/repo wc
Checked out revision 0.
$ svn info wc
Path: wc
URL: file:///d:/1/repo
Repository UUID: 3b81499e-e342-dd42-979c-4cc294580faf
Revision: 0
Node Kind: directory
Schedule: normal
Last Changed Rev: 0
Last Changed Date: 2005-06-20 12:29:02 -0600 (Mon, 20 Jun 2005)
$
---------------------------------------------------------------------

...

[Mark Parker]

What I listed was a transcript (it was a cut-and-paste from my terminal)
of me doing exactly this: creating an empty repository with no revisions
and checking it out at revision zero. I also checked out the repository
over http and svn:// protocols. There isn't anything in subversion that
requires there to be a revision greater than 0 in the repository to
check it out.

My server and client are both 1.2.0, but I've also done the exact same
thing many times with 1.1.x server/client combinations. I tried the
whole test (minus http:// protocol) with 1.0.5 client and server, and
the results are the same.

For some reason your client is attempting to check out revision 1 of the
repository. I don't know why it would do that. I'm just trying to point
out that the import-one-revision explanation might be a wild goose chase.

Mark

Post by Monks, Peter
G'day Mark,
I'm not sure I understand what your example is demonstrating. I'm
accessing a 1.0.5 server from a 1.2.0 client over the svn:// protocol.
AFAICT you're using the same (unknown) version of SVN for both the
client and the server and using the file:// protocol - something that
is quite different and hence quite possibly doesn't exhibit the
behaviour that I'm seeing. What Olivier described is a workaround
to the problem I'm seeing, albeit one that requires that I access the
repository using something other than a remote 1.2.0 client.
Perhaps you could explain your example in a bit more detail?
Thanks!
Peter
----------------------------------------------------------------------
Peter Monks http://www.sydneyclimbing.com/
----------------------------------------------------------------------

-----Original Message-----
Sent: Monday, June 20, 2005 11:33am
To: Olivier Sannier
Subject: Re: "svn: No such revision '1'" error during checkout

Post by Olivier Sannier
I think you need to do at least one commit before actually doing a
checkout.

No, definately not.
$ svnadmin create repo
$ svn co file:///d:/1/repo wc
Checked out revision 0.
$ svn info wc
Path: wc
URL: file:///d:/1/repo
Repository UUID: 3b81499e-e342-dd42-979c-4cc294580faf
Revision: 0
Node Kind: directory
Schedule: normal
Last Changed Rev: 0
Last Changed Date: 2005-06-20 12:29:02 -0600 (Mon, 20 Jun 2005)
$
---------------------------------------------------------------------

---------------------------------------------------------------------
.

...

[k***@collab.net]

Post by Monks, Peter
G'day everyone,
I just created a new repository on our trusty SVN 1.0.5 server, and
attempted to check it out using TortoiseSVN 1.2.0 as well as the SVN
1.2.0 command line client and in both cases I get the following error
svn: No such revision '1'
svn checkout svn://fu.bar.com/path/to/repos
svn checkout svn://fu.bar.com/path/to/repos/
svn checkout -r HEAD svn://fu.bar.com/path/to/repos/
svn checkout -r {2005-06-20} svn://fu.bar.com/path/to/repos/
When I tried checking out the BASE revision, the error message changed
svn: Bogus revision information given
Did I muck something up or is this an incompatibility between 1.2
clients and a 1.0 server?
Server: SVN 1.0.5 from sunfreeware.com running on SPARC Solaris 5.9
Client 1: TortoiseSVN 1.2.0 build 3602 from tigris.org running on
Windows 2000
Client 2: SVN 1.2.0 from tigris.org running on Windows 2000

...

This is very bizarre.

Do you have administrative access to the repository? Can you
successfully run 'svnadmin dump > /dev/null' on it?

What directory are you in on the client side when you run this? Is
there a working copy named 'repos' there?

[Monks, Peter]

G'day Karl,

Post by k***@collab.net
This is very bizarre.

Yeah, and I don't recall seeing it with pre-1.2 clients connecting to
the
same 1.0.5 server, although it's been a while since I created a new
repos on it, so there's a chance the last time I did this I was using a
1.0.x client.

Post by k***@collab.net
Do you have administrative access to the repository?

Yep.

Post by k***@collab.net
Can you successfully run 'svnadmin dump > /dev/null' on it?

Yep. The output was:

* Dumped revision 0.

Post by k***@collab.net
What directory are you in on the client side when you run this?

C:\Dev\test

Post by k***@collab.net
Is there a working copy named 'repos' there?

Nope - I created the "test" directory afresh straight after creating
the repository. Most of the subdirectories under C:\Dev are also
working copies (from different repositories / URLs), but they're each
contained in a dedicated subdirectory. Would that be causing issues,
perhaps? There is no "C:\Dev\.svn" directory so it isn't (or
shouldn't be!) a working copy.

Attached are transcripts of what I ran on the server, and then on the
client.

Cheers,
Peter

PS. I stand corrected - we're running on SVN 1.0.4, not 1.0.5. I
guess it's about time I got cracking on the long-delayed upgrade.
;-)

----------------------------------------------------------------------
Peter Monks http://www.sydneyclimbing.com/
***@sydneyclimbing.com http://www.geocities.com/yosemite/4455/
----------------------------------------------------------------------

[k***@collab.net]

Can you get an ethereal trace? I'd love to see what the client is
asking the server for...

-Karl

Post by Monks, Peter
G'day Karl,

Post by k***@collab.net
This is very bizarre.

Yeah, and I don't recall seeing it with pre-1.2 clients connecting to
the
same 1.0.5 server, although it's been a while since I created a new
repos on it, so there's a chance the last time I did this I was using a
1.0.x client.

Post by k***@collab.net
Do you have administrative access to the repository?

Yep.

Post by k***@collab.net
Can you successfully run 'svnadmin dump > /dev/null' on it?

* Dumped revision 0.

Post by k***@collab.net
What directory are you in on the client side when you run this?

C:\Dev\test

Post by k***@collab.net
Is there a working copy named 'repos' there?

Nope - I created the "test" directory afresh straight after creating
the repository. Most of the subdirectories under C:\Dev are also
working copies (from different repositories / URLs), but they're each
contained in a dedicated subdirectory. Would that be causing issues,
perhaps? There is no "C:\Dev\.svn" directory so it isn't (or
shouldn't be!) a working copy.
Attached are transcripts of what I ran on the server, and then on the
client.
Cheers,
Peter
PS. I stand corrected - we're running on SVN 1.0.4, not 1.0.5. I
guess it's about time I got cracking on the long-delayed upgrade.
;-)
----------------------------------------------------------------------
Peter Monks http://www.sydneyclimbing.com/
----------------------------------------------------------------------

...