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

Re: svn WC corruption issues with 1.5.3 client

From: Murli Varadachari <mvaradachari_at_facebook.com>
Date: Thu, 22 Jan 2009 08:53:50 -0800

On 1/22/09 12:59 AM, "Ryan Schmidt" <subversion-2009a_at_ryandesign.com> wrote:

On Jan 21, 2009, at 19:41, Murli Varadachari wrote:

> I am currently using svn 1.5.3. Since my conversion to 1.5.3 [ both
> client / server ] I have noticed on several occasions
> problems when attempting to update my WC. The WC in question has no
> user level modifications and I was just trying
> to bring it up to date.
> Error message ==>>
> # cd /usr/local/fbprojects/releases/blogfeeds-trunk/
> # svn up
> svn: Can't open file 'utils/.svn/text-base/
> fix_nonupdating_feeds.py.svn-base': No such file or directory
> ==>>
> The .svn/entries file has reference to this file
> "fix_nonupdating_feeds.py.svn-base" but this file is missing in
> the .svn/text-base
> To fix this I had to remove the entire directory "utils/" and svn
> up from one level above.
> A few other engineers have reported similar problems as well.

>>Do you have another file in this directory whose name differs only in
>>case (e.g. perhaps fix_nonupdating_feeds.PY), and are you on a case-
>>insensitive filesystem?

This is a linux system and there is only one version of the above file.

> Are there any know bugs / issues with svn 1.5.3 ?

>>I would say obviously yes, otherwise there wouldn't have been 1.5.4
>>and 1.5.5 versions. :)

True - but my Q was specific to the above issues.



To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-01-22 17:54:57 CET

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.