You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by claudia logan <cv...@yahoo.com> on 2008/02/04 12:58:15 UTC

Re: Error message, plse help decipher it

Hi all,
    Yes, we can actually checkout and update the repo. So I am not sure why we receive this message at the end of each update/checkout.  Our repo is accessed through http,both via command line and TortoiseSVN, Here is our versions:
 
Ubuntu 6.10  
Linux 2.6.17
Apache 2.0.55
Subversion 1.3.2
 
I looked on the svn manual, and couldnt find any reference to this error: PROPFIND  So I am not sure what it means, other than it couldn't access the path.  We did recently reconfigure the directory structure within subversion, so my guess is that is looking for the old path...but, wouldn't subversion know this?...
As mentioned, we can access and update as appropriate, but would like to fix it and resolve the error. 
 
Help !


----- Original Message ----
From: Ryan Schmidt <su...@ryandesign.com>
To: claudia logan <cv...@yahoo.com>
Cc: users@subversion.tigris.org
Sent: Thursday, January 31, 2008 9:18:31 AM
Subject: Re: Error message, plse help decipher it


On Jan 31, 2008, at 08:06, claudia logan wrote:

>    Have a quick question, during a recent checkout and update, the  
> following error occured:
>
> svn: PROPFIND request failed on '/path to repo/tags
> svn: could not open the requested SVN filesystem.
>
> The complete repository was checked out and all files were  
> available, however, every time we try to Update, we keep getting  
> this error.


Please confirm: you can check out a working copy from this repository  
right now and it works, but then immediately doing an update in that  
new working copy fails with the above message? It shouldn't be,  
because the message means it cannot find your repository on the  
server's hard disk, but if the checkout worked, then it obviously  
could find it.

You could help us more by telling us the version of Subversion on the  
client and the server, the OS on the client and the server, the  
repository access method, and, if you're using apache, the apache  
configuration for the repository.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org


      ____________________________________________________________________________________
Be a better friend, newshound, and 
know-it-all with Yahoo! Mobile.  Try it now.  http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ 

Re: Error message, plse help decipher it

Posted by John Waycott <ja...@cox.net>.
Ryan Schmidt wrote:
> On Feb 4, 2008, at 06:58, claudia logan wrote:
>
>>> On Jan 31, 2008, at 08:06, claudia logan wrote:
>>>
>>> >    Have a quick question, during a recent checkout and update, the
>>> > following error occured:
>>> >
>>> > svn: PROPFIND request failed on '/path to repo/tags
>>> > svn: could not open the requested SVN filesystem.
>>> >
>>> > The complete repository was checked out and all files were
>>> > available, however, every time we try to Update, we keep getting
>>> > this error.
>>>
>>> Please confirm: you can check out a working copy from this repository
>>> right now and it works, but then immediately doing an update in that
>>> new working copy fails with the above message? It shouldn't be,
>>> because the message means it cannot find your repository on the
>>> server's hard disk, but if the checkout worked, then it obviously
>>> could find it.
>>>
>>> You could help us more by telling us the version of Subversion on the
>>> client and the server, the OS on the client and the server, the
>>> repository access method, and, if you're using apache, the apache
>>> configuration for the repository.
>>
>>     Yes, we can actually checkout and update the repo. So I am not 
>> sure why we receive this message at the end of each update/checkout. 
>> Our repo is accessed through http,both via command line and 
>> TortoiseSVN, Here is our versions:
>>
>> Ubuntu 6.10
>> Linux 2.6.17
>> Apache 2.0.55
>> Subversion 1.3.2
>>
>> I looked on the svn manual, and couldnt find any reference to this 
>> error: PROPFIND  So I am not sure what it means, other than it 
>> couldn't access the path.  We did recently reconfigure the directory 
>> structure within subversion, so my guess is that is looking for the 
>> old path...but, wouldn't subversion know this?...
>> As mentioned, we can access and update as appropriate, but would like 
>> to fix it and resolve the error.
>
> I still haven't understood when exactly the problem occurs.
>
> First you said it occurs during checkout and update: "during a recent 
> checkout and update, the following error occured"
>
> Later in that same message you said checkout works but update doesn't: 
> "The complete repository was checked out and all files were available, 
> however, every time we try to Update, we keep getting this error"
>
> Now you say you can both checkout and update: "Yes, we can actually 
> checkout and update the repo"
>
> And then in the next sentence you say checkout and update don't work: 
> "we receive this message at the end of each update/checkout"
>
> And then at the end you say "we can access and update as appropriate" 
> which sounds again like update is working, though I don't know what 
> specifically you mean by "access".
>
> So these various statements are rather contradictory and confusing.
>
> Please show us the "svn checkout" command you run and the output it 
> produces. And also please show what happens when you then run "svn 
> update" on the same working copy.
>
> Is the issue intermittent or does it happen all the time? To all your 
> users or just some? We need more information.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
>
Could a bad svn:externals property cause this error? I vaguely remember 
something like this in one of our projects that turned out to be misuse 
of svn:externals.



---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: Error message, plse help decipher it

Posted by Ryan Schmidt <su...@ryandesign.com>.
On Feb 4, 2008, at 06:58, claudia logan wrote:

>> On Jan 31, 2008, at 08:06, claudia logan wrote:
>>
>> >    Have a quick question, during a recent checkout and update, the
>> > following error occured:
>> >
>> > svn: PROPFIND request failed on '/path to repo/tags
>> > svn: could not open the requested SVN filesystem.
>> >
>> > The complete repository was checked out and all files were
>> > available, however, every time we try to Update, we keep getting
>> > this error.
>>
>> Please confirm: you can check out a working copy from this repository
>> right now and it works, but then immediately doing an update in that
>> new working copy fails with the above message? It shouldn't be,
>> because the message means it cannot find your repository on the
>> server's hard disk, but if the checkout worked, then it obviously
>> could find it.
>>
>> You could help us more by telling us the version of Subversion on the
>> client and the server, the OS on the client and the server, the
>> repository access method, and, if you're using apache, the apache
>> configuration for the repository.
>
>     Yes, we can actually checkout and update the repo. So I am not  
> sure why we receive this message at the end of each update/ 
> checkout. Our repo is accessed through http,both via command line  
> and TortoiseSVN, Here is our versions:
>
> Ubuntu 6.10
> Linux 2.6.17
> Apache 2.0.55
> Subversion 1.3.2
>
> I looked on the svn manual, and couldnt find any reference to this  
> error: PROPFIND  So I am not sure what it means, other than it  
> couldn't access the path.  We did recently reconfigure the  
> directory structure within subversion, so my guess is that is  
> looking for the old path...but, wouldn't subversion know this?...
> As mentioned, we can access and update as appropriate, but would  
> like to fix it and resolve the error.

I still haven't understood when exactly the problem occurs.

First you said it occurs during checkout and update: "during a recent  
checkout and update, the following error occured"

Later in that same message you said checkout works but update  
doesn't: "The complete repository was checked out and all files were  
available, however, every time we try to Update, we keep getting this  
error"

Now you say you can both checkout and update: "Yes, we can actually  
checkout and update the repo"

And then in the next sentence you say checkout and update don't work:  
"we receive this message at the end of each update/checkout"

And then at the end you say "we can access and update as appropriate"  
which sounds again like update is working, though I don't know what  
specifically you mean by "access".

So these various statements are rather contradictory and confusing.

Please show us the "svn checkout" command you run and the output it  
produces. And also please show what happens when you then run "svn  
update" on the same working copy.

Is the issue intermittent or does it happen all the time? To all your  
users or just some? We need more information.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org