When upgrading awstats from 6.4 to 6.5, webapp-config gave the following as the command needed to update protected files: CONFIG_PROTECT="/var/www/localhost/htdocs/awstats" etc-update However, many of awstats' files are installed OUTSIDE this directory in /var/www/localhost/cgi-bin. Following the current instructions leaves over 100 files as ._cfg files which leaves awstats in a non- working state. Doing CONFIG_PROTECT="/var/www/localhost" etc-update fixes the problem. I am not sure whether this is a problem with webapp-config or awstats. I seriously question whether installing files outside the destination directory like awstats does is a correct use of webapp-config. Reproducible: Didn't try Steps to Reproduce: 1. emerge =awstats-6.4 2. webapp-config -I -h localhost -d awstats awstats 6.4 3. emerge awstats 4. webapp-config -U -h localhost -d awstats awstats 6.5 5. CONFIG_PROTECT="/var/www/localhost/htdocs/awstats" etc-update Actual Results: Over 100 ._cfg* files in /var/www/localhost/cgi-bin tree leaves at least parts of awstats non-functional Expected Results: webapp-config should have recommended CONFIG_PROTECT="/var/www/localhost" etc-update i.e. the host directory rather than the app directory OR webapp-config should overwrite the files in /var/www/localhost/cgi-bin rather than protect them OR awstats' webapp-config install should install all its files under the awstats directory. I've marked this critical as the result for me was to lose at least an hour's worth of statistics data on multiple domains. Others users could lose more (or less) data depending on how they use awstats.
sorry, webapp-config version is 1.11
Thanks for the note. I implemented a fix in the next version of webapp-config.
Fixed upstream
