When installing xoops, then configuring it, removing it and then reinstalling it again, the file mainfile.php get's overwritten. Example: 1) /usr/sbin/webapp-config -I -h localhost -V -u apache -d /xoops 2.0.7.3 2) Then use a web browser to configure xoops 3) Remove /xoops/install and chmod 444 mainfile.php (as advised by webapp-config) 4) Then uninstall xoops: /usr/sbin/webapp-config -C -h localhost -V -u apache -d /xoops 2.0.7.3 (mainfile.php does not get deleted! This is good) 5) Then reinstall xoops: /usr/sbin/webapp-config -I -h localhost -V -u apache -d /xoops 2.0.7.3 6) BANG!! mainfile.php get's overwritten by webapp-config I think that the ebuild for xoops needs to add mainfile.php as webapp_configfile. Without that the file is handled as a normal script file and this is sure not the case. Reproducible: Always Steps to Reproduce: 1. 2. 3.
ups, I've made a confusion; thought it was about www-proxy/oops. sorry...
this update (79348, 2.0.11 ebuild) also solves this problem....
This is interesting. From what I understand, this is a bug in webapp-config: 1. webapp-config -C -d xoops xoops 2. webapp-config -I -d xoops xoops 2.0.13 That overwrites files that are marked as webapp_configfile. Nico - no, marking as webapp_configfile doesn't seem to work. Stu - thoughts? Reassigning (also note the version bump).
Fixed by webapp-config v1.50
