I emerged subversion without apache2 in my USE flags. When I did as I was told, and ran ebuild config, I encountered this error: # ebuild /usr/portage/dev-util/subversion/subversion-1.2.3-r2.ebuild config * >>> Initializing the database in /var/svn... * >>> Populating repository directory ... * >>> Setting repository permissions ... chown: `apache:apache': invalid user Nothing critical, really ;-)
Hmm. perhaps without the apache useflag we should not change the ownership at all. Otherwise I could remove the whole config option.
(In reply to comment #1) > Hmm. perhaps without the apache useflag we should not change the ownership at > all. Otherwise I could remove the whole config option. > svnserve seems to be set to run as apache by default, however. That needs to be changed as well.
But svnserve should not run as root. That would mean creating a separate subversion user. Basically, there must be a user for subversion. When the apache module is used, this user should be apache. Otherwise it can be a different one. While other setups are possible, they are too complex for in the ebuild.
Oh, I forgot to add this: # /etc/init.d/svnserve start * Starting svnserve ... start-stop-daemon: group `apache' not found
Ideally, in the event of the USE flag apache being there, use apache:apache for user and group. With -apache, create an svn user and svn group.
Created attachment 101741 [details] ebuild for 1.3.2 with creation of svn:svnusers if -apache2 Hi, This ebuild creates the svn:svnusers user if -apache2 is used, sets the permissions of /var/svn/repos accordingly and installs the following confd file. Cheers, Olivier
Created attachment 101742 [details] confd file with svn:svnusers user and group
Created attachment 101743 [details] ebuild for 1.4.0 with creation of svn:svnusers if -apache2
*** Bug 179175 has been marked as a duplicate of this bug. ***
This bug seems to be fixed.
