Subversion Update Issue
Environment
- Red Hat Enterprise Linux 5
- subversion 1.6
Issue
- Customer upgraded a server from 5.3 to 5.7.
- Subversion was updated but the /etc/sysconfig/svnserve file was removed and not replaced or backed up.
# grep subv /var/log/yum.log
Jan 24 16:18:10 Updated: subversion-1.6.11-7.el5_6.4.x86_64
Jan 24 16:20:34 Updated: subversion-1.6.11-7.el5_6.4.i386
- It appears that /etc/sysconfig/svnserve is not provided in the subversion RPM.
- Customer believes this is an error, that it should either not remove the file or backup the file if it was going to replace it.
[root@q ~]# rpm -ql subversion-1.6.11-7.el5_6.4.x86_64 | grep svnserve
/etc/rc.d/init.d/svnserve
/usr/bin/svnserve
/usr/share/doc/subversion-1.6.11/tools/examples/svnserve-sgid.c
/usr/share/man/man5/svnserve.conf.5.gz
/usr/share/man/man8/svnserve.8.gz
Resolution
- The Red Hat RPM does not own the /etc/sysconfig/svnserve.
- The Red Hat RPM init script will source this file, if it exists, to set the OPTIONS variable to use for startup flags.
- These daemon's flags will allow you to set the root for repositories server (--root=) and/or a global configuration file if you don't want to use the per-repository configurations (and other options).
- While the Red Hat RPM does not own the /etc/sysconfig/svnserve file, it will utilize it if it exists.
- It is an admin owned file and therefore any installs/update/removals of the Red Hat RPM should not have an impact to the /etc/sysconfig/svnserve config file that the init script will source if present for daemon OPTIONS.
This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.
