[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Error message, plse help decipher it

From: claudia logan <cvlogan1_at_yahoo.com>
Date: Sat, 9 Feb 2008 11:21:21 -0800 (PST)

Ahhhh !! Yes, some time ago (prior to joining this shop), the use of externals were used and several tags were created with externals. As mentioned earlier, we reconfigured the directory structure within the repository to make better use of shared files/directories.

Thank you, thank you, THANK YOU !!!

So how do I reconfigure the externals to meet the new configuration? I am a little fussy when it comes to externals and this is after reading it on the manual :-( . Based on what I have read, it deals with very generic stuff but does not touch on reconfiguring...Help !

----- Original Message ----
From: John Waycott <javajohn_at_cox.net>
To: Ryan Schmidt <subversion-2007b_at_ryandesign.com>
Cc: claudia logan <cvlogan1_at_yahoo.com>; users_at_subversion.tigris.org
Sent: Friday, February 8, 2008 9:06:23 AM
Subject: Re: Error message, plse help decipher it

 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_at_subversion.tigris.org
> For additional commands, e-mail: users-help_at_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_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org

      ____________________________________________________________________________________
Never miss a thing. Make Yahoo your home page.
http://www.yahoo.com/r/hs
Received on 2008-02-09 20:21:46 CET

This is an archived mail posted to the Subversion Users mailing list.