Forwarding to the new mailing list. It would be nice to get some form of acknowledgement, someone trying to replicate the issue at least. I'd file a bug but again the buddy system suggests I should post here or on IRC and at the moment I'm getting a whole lot of dead air. Perhaps I need more patience.
Steps to replicate are simple: Step 1) grab your friendly AuthzSVNAccessFile Step 2) Add a [groups:/] section with perhaps a token entry. Step 3) Test Step 4) Reply to list with test results and versions. Cheers, Sam ---------- Forwarded message ---------- From: Sam Moffatt <sam.moff...@joomla.org> Date: Sun, Nov 15, 2009 at 4:19 PM Subject: Error with AuthzSVNAccessFile parsing in mod_dav_svn To: us...@subversion.tigris.org Hi all, I think I've found a bug in the way that AuthzSVNAccessFile is parsed. I recently upgraded an old Subversion 1.2.1 site with some projects to first 1.4.2 and then 1.6.6 and discovered that the file balked at loading and spat out the following error: Failed to load the AuthzSVNAccessFile: An authz rule refers to group '@groups-committers', which is undefined I went hunting figuring a script somewhere had died but couldn't work out what was going wrong because as far as I could see the group did exist. I then looked to the section that was causing the issue: [groups:/] @groups-committers = rw @groups-readers = r * = r I removed the committers line and tested again, it then complained about groups-readers, so I removed that line. That then yielded an even strange error message: Failed to load the AuthzSVNAccessFile: An authz rule refers to group '*', which is undefined At this point I deleted the last two lines of the section and everything came good. Then I put the section back and it broke it. I renamed it from 'groups' to 'tgroups' and it started working again. I then changed it to 'groupstest' and it still triggered an error. Subversion 1.2 (CentOS 4) was working happily with this, both 1.4.2 (CentOS 4 packages) and 1.6.6 (RPMForge) exhibited the incorrect behaviour. Cheers, Sam
