Re: [viewvc-users] authz rules not being followed when folder name doesn't match Location name.

"C. Michael Pilato" <[email protected]>
Newsgroups gmane.comp.version-control.cvs.viewcvs.user
Organization CollabNet, Inc.
Message-ID <[email protected]>
Terr Dooher wrote:
> But I think ViewVC is using the repo path component (proj12) in deciding
> on permissions and hence not allowing me to see, or enter it. (Manually
> adding /proj12 to the URL results in a 404).
> 
> Is this a bug, or I have I just highlighted an unsupported svn setup?

Your setup (of ViewVC) doesn't jive with your Subversion setup, and that's
where the problem lies.  I think if you switched to using svn_roots= (which
allows you to explicitly name each root) instead of root_parents= (which
derives root names from the basename of the containing directory), your
configuration will work.

To be clear, instead of doing this:

   root_parents = /var/svn : svn

You should switch to something like this (where you list all 20 repositories
for each vhost, or all repositories if you're only using one vhost in ViewVC):

   svn_roots = proj : /var/svn/proj,
               ...
               svn : /var/svn/proj12,
               ...

Yes, this unfortunately means that every time you add a new repository, you
have to edit viewvc.conf.  But you already have to do this for httpd.conf
(since you aren't using SVNParentPath), so this is just one more small step.

-- 
C. Michael Pilato <[email protected]>
CollabNet   <>   www.collab.net   <>   Distributed Development On Demand

------------------------------------------------------
http://viewvc.tigris.org/ds/viewMessage.do?dsForumId=4255&dsMessageId=2619231

To unsubscribe from this discussion, e-mail: [[email protected]].
signature.asc (application/pgp-signature, 197 B)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAkwQ3SoACgkQokEGqRcG/W45jwCfd+M88Urk+riVopLrwZBQSpNI
y2QAni8AZIEqosYGPWWNwvrwtp0lQvEn
=hjf9
-----END PGP SIGNATURE-----
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.