Am 18.07.2012 10:58, schrieb Guillaume Rousse:
Installing from scratch will trigger the failure, I forgot to make the
script specific to upgrade scenario only. However, it's unclear why it
fails when upgrading from a previous installation (for you), where
/etc/httpd/conf directory exist, but not /etc/httpd/conf/sites.d:
# prevent symlink creation failure on update
if [ ! -d /etc/httpd/conf/sites.d ]; then
mkdir /etc/httpd/conf/sites.d
mv -f /etc/httpd/conf/webapps.d/* /etc/httpd/conf/sites.d 2>/dev/null
mv -f /etc/httpd/conf/vhosts.d/* /etc/httpd/conf/sites.d 2>/dev/null
rmdir /etc/httpd/conf/webapps.d
rmdir /etc/httpd/conf/vhosts.d
fi
I guess it has something to do with exact package ordering during
uninstallation transaction. In the past we had %pretrans trigger, I'm
not sure it is still available.
Another short question while we are on it.
This does mean we have to change the web application packages (like
drupal, mediawiki,...) who have files in /etc/httpd/conf/webapps.d/,
doesn't it?
Oliver
