subversion-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Johan Corveleyn <jcor...@gmail.com>
Subject Re: Problem with My SVN Server
Date Tue, 04 Jan 2011 08:50:51 GMT
[ please don't top-post on this list, i.e. please put your reply at
the bottom, or inline, below the thing you're replying to. ]

On Tue, Jan 4, 2011 at 9:20 AM, santhosh kumar <santhoshkallar@gmail.com> wrote:
> On Mon, Dec 20, 2010 at 12:56 PM, santhosh kumar <santhoshkallar@gmail.com>
> wrote:
>>
>>
>> ---------- Forwarded message ----------
>> From: Johan Corveleyn <jcorvel@gmail.com>
>> Date: Mon, Dec 20, 2010 at 12:55 AM
>> Subject: Re: Problem with My SVN Server
>> To: Nico Kadel-Garcia <nkadel@gmail.com>
>> Cc: santhoshkallar@gmail.com, users@subversion.apache.org
>>
>>
>> On Sun, Dec 19, 2010 at 6:11 PM, Nico Kadel-Garcia <nkadel@gmail.com>
>> wrote:
>> > On Fri, Dec 17, 2010 at 9:30 AM, santhosh kumar
>> > <santhoshkallar@gmail.com> wrote:
>> >> Hi
>> >>
>> >> This is Santhosh Kumar from Bangalore, I have a chat with Mr. C.
>> >> Michael
>> >> Pilato regarding a problem with My SVN Server, he suggested me to
>> >> contact in
>> >> this mail id.
>> >>
>> >> I am expecting a positive output from your group.
>> >>
>> >>
>> >> I have a svn server, I was using it for the past 6-8 months without any
>> >> problem.
>> >>
>> >> The problem is that, I am not able to check out a file from the svn
>> >> server
>> >> system. But the same file can be checked out from any other linux box.
>> >>
>> >> From the server I wanted to checkout the same file for some script. It
>> >> is a
>> >> tar.bz2 file
>> >>
>> >> The error is
>> >>
>> >> svn: Can't open file 'flse/.svn/tmp/text-base/pgms.tar.bz2.svn-base':
>> >> Permission denied.
>> >>
>> >> But the same file I am able to do a check out from another linux box. I
>> >> am
>> >> running the checkout as root user- having all permission.
>> >>
>> >> Request you to assist me with this.
>> >>
>> >> with hopes..........
>> >>
>> >> Santhosh Kumar K V
>> >
>> > Well, the error message seems pretty clear. You can't open
>> > "'flse/.svn/tmp/text-base/pgms.tar.bz2.svn-base". Check the
>> > permissions, and contents, of the relevant directory and files.
>> >
>> > Personally, I'd wonder if you'd accidentally screwed up your working
>> > copy by some other issue, such as running out of space in the midst of
>> > a checkout. And I'd consider making a clean new checkout to a new
>> > workspace, and comparing its contents to your existing working copy.
>>
>> Also, you may want to check for a "case-conflict" of that particular
>> file inside your repository. I.e. two files with filenames that only
>> differ in case (e.g. pgms.tar.bz2 and Pgms.tar.bz2). This can give
>> problems when checking out on a case-insensitive filesystem (which may
>> manifest itself with an error such as this one).
>>
> Thanks for your support, But the problem still remains

You'll have to provide some more information if you want to help other
people help you :-).

What did you try?

- Did you check the permissions/ownership of the file
'flse/.svn/tmp/text-base/pgms.tar.bz2.svn-base' on the client that's
having the problem?

- What's the filesystem on the client where you're having the problem?
Is the working copy by any chance on a remote disk, mounted via NFS or
CIFS? If so, is it by any chance a shared working copy, with other
users or clients from other PC's accessing it as well?

- What's the exact OS on the client having the problem? Any specific
differences with the "other linux boxes" that don't have the problem?

- Did you look at the repository, to see if there is maybe a
"case-conflict" (two files with filenames only differing in case)?
What's the output of "svn ls $REPOS_URL/$SUBDIR/flse"?

- If all else fails, a workaround is to simply check out a new working
copy (and transfer your outstanding local modifications from the
broken working copy to the new one manually (or automatically, by
copying all files from the old to the new, but excluding .svn
directories)). That is: if the problem does not re-appear in your new
working copy ...

HTH,
-- 
Johan

Mime
View raw message