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

RE: Problem

From: Bert Huijben <bert_at_qqmail.nl>
Date: Wed, 4 Sep 2013 19:52:01 +0200

> -----Original Message-----
> From: Bert Huijben [mailto:bert_at_qqmail.nl]
> Sent: woensdag 4 september 2013 18:16
> To: 'Thorsten Schöning'; users_at_subversion.apache.org
> Subject: RE: Problem
>
>
>
> > -----Original Message-----
> > From: Thorsten Schöning [mailto:tschoening_at_am-soft.de]
> > Sent: woensdag 4 september 2013 12:25
> > To: users_at_subversion.apache.org
> > Subject: Re: Problem
> >
> > Guten Tag odd oddorks,
> > am Mittwoch, 4. September 2013 um 09:33 schrieben Sie:
> >
> > > I think the problem derivate to the directory unaccessible because
> > > if I elevate my user the problem do not exist anymore.
> > [...]
> > > The problem was not present on version 1.6.x
> >
> > I can't believe that a switch in your version of Subversion changes
> > anything regarding access permissions in your working copy. Subversion
> > 1.8 could even be more compatible because it only needs write access
> > to one svn folder. Are you really sure nothing else changed the
> > permissions in your working copy? What do the permissions look like at
> > all? Where are the working copies stored, in your home directory or
> > elsewhere?
> >
> > I have a restricted user myself and dozens of working copies and no
> > problems with permissions.
>
> Just a guess:
>
> Do you have file externals in this working copy?
>
> And if yes: Is one of these affected by the update? (Perhaps something was
> added in its place?)

Or there is an explicit authz setting in the repository that nothing can be
added in its place?

        Bert
Received on 2013-09-04 19:53:05 CEST

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.