Bug 167639 - policycoreutils could be a dependency of mod_dav_svn or httpd?
policycoreutils could be a dependency of mod_dav_svn or httpd?
Status: CLOSED NOTABUG
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: subversion (Show other bugs)
4.0
All Linux
medium Severity low
: ---
: ---
Assigned To: Joe Orton
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2005-09-06 11:06 EDT by Dimitri Papadopoulos
Modified: 2007-11-30 17:07 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2005-09-06 11:18:22 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Dimitri Papadopoulos 2005-09-06 11:06:10 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; fr-FR; rv:1.7.10) Gecko/20050717 Firefox/1.0.6

Description of problem:
File /etc/httpd/conf.d/subversion.conf contains the following comment:
#
# Example configuration to enable HTTP access for a directory
# containing Subversion repositories, "/var/www/svn".  Each repository
# must be readable and writable by the 'apache' user.  Note that if
# SELinux is enabled, the repositories must be labelled with a context
# which httpd can write to; this will happen by default for
# directories created in /var/www.  Use "restorecon -R /var/www/svn"
# to label the repositories if upgrading from a previous release.
#

I can't find "restorecon":
	# locate restorecon
	# 

Oh, it's actually in package policycorutils:
	# up2date -i policycoreutils
	# rpm -qf /sbin/restorecon
	policycoreutils-1.18.1-4.3
	# 

Maybe "policycoreutils" should be installed when installing Apache - a dependency? Or maybe it should be always installed?


Version-Release number of selected component (if applicable):
mod_dav_svn-1.1.1-2.1

How reproducible:
Always

Steps to Reproduce:
1. cat /etc/httpd/conf.d/subversion.conf


Additional info:
Comment 1 Joe Orton 2005-09-06 11:18:22 EDT
restorecon is just given as an example of how to label the directory if this is
an upgrade and an old unlabelled directory exists.  If the directory is created
from new, restorecon is not needed.  chcon from coreutils could equally well be
used, in any case; the package itself has no requirement on restorecon.

Note You need to log in before you can comment on or make changes to this bug.