You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Matthew Slowe <m....@kent.ac.uk> on 2008/02/13 10:36:08 UTC
AuthZ + svn move + svn log = 403
Morning all,
I've had a quick scan of the docs and the mailing list archives and
can't find any reference to this problem so I thought I'd give you lot a
try.
Sorry this is a little convoluted but any ideas would be appreciated...
=== Backstory ===
We had some *old* sccs repos to drag up-to-date so each one was
converted using sccs2svn.py and then loaded into an existing repository.
This was done one at a time so that the files from each sccs repo could
be moved appropriately within the new svn repo:
$ sccs2svn ... in=olddir1 out=dir.svn
$ svnadmin dump dir.svn | svnadmin load existing.svn
-> checkout existing.svn
$ svn mkdir new/tree/olddir1
$ svn move <new files> new/tree/olddir1
... then proceed on to next olddir. This all worked ok and the logs etc
were loaded in (which is really what I was after -- preservation of
changelogs).
The new svn repo is under the control of an AuthzSVNAccessFile which
looks like this:
[existing.svn:/]
@users = rw
[existing.svn:/new/tree/olddir1]
@otherusers = rw
=== Problem ===
Members of @users have no problem accessing anything.
Members of @otherusers have no problem accessing olddir1 as far as
checkouts, commites etc are concerned but have problems access logs
which go back to before the files containted therein were moved -- it
looks like svn log is traversing back up the tree to / where it hits a
403. Is this expected behaviour? If not, is it a bug?
Example:
$ svn info
Path: .
URL: https://xxx/svn/config/aphrodite/nadmin
Repository Root: https://xxx/svn/config
Repository UUID: a4215e26-b911-c670-e346-d994ef297a65
Revision: 558
Node Kind: directory
Schedule: normal
Last Changed Author: ms1
Last Changed Rev: 558
Last Changed Date: 2008-02-04 15:53:11 +0000 (Mon, 04 Feb 2008)
As a member of @users:
$ svn log -r 399 hostinfo
------------------------------------------------------------------------
r399 | root | 2007-01-19 12:20:31 +0000 (Fri, 19 Jan 2007) | 3 lines
remove croft_politics and croft_psychology
------------------------------------------------------------------------
As a member of @otherusers:
$ svn log -r 399 hostinfo
svn: PROPFIND request failed on '/svn/config/hostinfo'
svn: PROPFIND of '/svn/config/hostinfo': 403 Forbidden (https://xxx.kent.ac.uk)
Thanks,
--
Matthew Slowe <m....@kent.ac.uk> | Tel: +44 (0)1227 824265
Development Team, Information Services | Fax: +44 (0)1227 824078
University of Kent, Canterbury, Kent | Web: http://www.kent.ac.uk/
Re: AuthZ + svn move + svn log = 403
Posted by Matthew Slowe <m....@kent.ac.uk>.
Any ideas on the below?
On Wed, Feb 13, 2008 at 10:36:08AM +0000, Matthew Slowe wrote:
> Morning all,
>
> I've had a quick scan of the docs and the mailing list archives and
> can't find any reference to this problem so I thought I'd give you lot a
> try.
>
> Sorry this is a little convoluted but any ideas would be appreciated...
>
> === Backstory ===
>
> We had some *old* sccs repos to drag up-to-date so each one was
> converted using sccs2svn.py and then loaded into an existing repository.
>
> This was done one at a time so that the files from each sccs repo could
> be moved appropriately within the new svn repo:
>
> $ sccs2svn ... in=olddir1 out=dir.svn
> $ svnadmin dump dir.svn | svnadmin load existing.svn
> -> checkout existing.svn
> $ svn mkdir new/tree/olddir1
> $ svn move <new files> new/tree/olddir1
>
> ... then proceed on to next olddir. This all worked ok and the logs etc
> were loaded in (which is really what I was after -- preservation of
> changelogs).
>
> The new svn repo is under the control of an AuthzSVNAccessFile which
> looks like this:
>
> [existing.svn:/]
> @users = rw
>
> [existing.svn:/new/tree/olddir1]
> @otherusers = rw
>
> === Problem ===
>
> Members of @users have no problem accessing anything.
>
> Members of @otherusers have no problem accessing olddir1 as far as
> checkouts, commites etc are concerned but have problems access logs
> which go back to before the files containted therein were moved -- it
> looks like svn log is traversing back up the tree to / where it hits a
> 403. Is this expected behaviour? If not, is it a bug?
>
> Example:
>
> $ svn info
> Path: .
> URL: https://xxx/svn/config/aphrodite/nadmin
> Repository Root: https://xxx/svn/config
> Repository UUID: a4215e26-b911-c670-e346-d994ef297a65
> Revision: 558
> Node Kind: directory
> Schedule: normal
> Last Changed Author: ms1
> Last Changed Rev: 558
> Last Changed Date: 2008-02-04 15:53:11 +0000 (Mon, 04 Feb 2008)
>
>
> As a member of @users:
> $ svn log -r 399 hostinfo
> ------------------------------------------------------------------------
> r399 | root | 2007-01-19 12:20:31 +0000 (Fri, 19 Jan 2007) | 3 lines
>
> remove croft_politics and croft_psychology
>
>
> ------------------------------------------------------------------------
>
>
> As a member of @otherusers:
> $ svn log -r 399 hostinfo
> svn: PROPFIND request failed on '/svn/config/hostinfo'
> svn: PROPFIND of '/svn/config/hostinfo': 403 Forbidden (https://xxx.kent.ac.uk)
>
>
>
>
> Thanks,
>
> --
> Matthew Slowe <m....@kent.ac.uk> | Tel: +44 (0)1227 824265
> Development Team, Information Services | Fax: +44 (0)1227 824078
> University of Kent, Canterbury, Kent | Web: http://www.kent.ac.uk/
--
Matthew Slowe <m....@kent.ac.uk> | Tel: +44 (0)1227 824265
Development Team, Information Services | Fax: +44 (0)1227 824078
University of Kent, Canterbury, Kent | Web: http://www.kent.ac.uk/