tag 692013 -unreproducible -moreinfo
reassign 692013 php5
retitle 692013 php5-* modules: fails to install and uninstall if the config
file was removed by user
thanks
On Fri, Nov 02, 2012 at 05:09:00PM +0100, Tobias Frost wrote:
> > Anyway, this bug should belong to php5enmod/php5dismod (package php5),
> > but I think it's not a bug. E.g., a2enmod/a2dismod works same way: it
> > fails with non-zero exit status if there is no config file in
> > mods-available/ dir.
>
> Disagree, because it is not php5 which fails to upgrade/deinstall.
First, it's. php5dismod belongs to this package and maintainers of
php5 suggests some stanzas in prerm/postrm scripts. Please, see #667775:
-->8--
if [ "$1" = "remove" ]; then
php5dismod mysqlnd
fi
-->8--
Thus, php5 core modules packages are affected as well:
http://anonscm.debian.org/gitweb/?p=pkg-php/php.git;a=blob;f=debian/php5-module.prerm
Second, it's not clear how to resolve this issue:
1) fix php5dismod to return 0 in this case
2) use "php5dismod xyz || true"
3) check return status $s of php5dismod and *not fail* for $s=2
>> E.g., a2enmod/a2dismod works same way: it
>> fails with non-zero exit status if there is no config file in
>> mods-available/ dir.
> Can you show me an example where aenmod fails
Yep.
# a2dismod blah-blah ; echo $?
ERROR: Module blah-blah does not exist!
1
Some apache modules uses "a2dismod xyz || true", some - just "a2dismod
xyz". I think - the first one is not a good choice. There is no way
at all to check exit status of a2dismod and then safe ignore *some*
errors (e.g. removed mod-available/xyz.conf).
Probably, both php5dismod/php5enmod (and a2dismod/a2enmod) should be
redesigned a lot to really fix this issue. That's why I suggest to
reassign this bug to php5 package first.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
