Bug#719266: apache2_invoke enconf ignores dependencies disabled by admin
Hi Stefan I think there is some confusion: > Think about this situation: > - admin needs proxy, enables it > - admin no longer needs proxy, disables it again > - admin installs package that needs proxy > So, having a wait to prevent modules from being autmatically enabled > would be nice, but it would have to be an explicit setting and not the > default behavior. I kinda agree. But that was not my not point: When a module is explicitly disabled by site administrator, then a package tries to enable it back, he's getting an error like: # apache2_invoke enmod proxy apache2_invoke proxy: no action - module was disabled by maintainer But when a package tries to enable a module that depends on the one explicitly disabled, both are enabled with no error. My report was about that inconsistency. Should that report be split to clarify the "explicitly disabled" part? Or do you have an idea about what "explicitly disabled" means, so that the so called inconsistency is irrelevent? signature.asc Description: This is a digitally signed message part.
Bug#719266: apache2_invoke enconf ignores dependencies disabled by admin
Am Freitag, 9. August 2013, 21:53:01 schrieb Jean-Michel Vourgère: > If sysop disabled a module, then a maintainer script enable a module > that depends on the first one, they are both enabled, ignoring > admin choice. > > Example (from a fresh wheezy install upgraded to jessie): > > # a2enmod proxy > Enabling module proxy. > # a2dismod proxy > Module proxy disabled. > # a2query -m proxy > No module matches proxy (disabled by site administrator) Think about this situation: - admin needs proxy, enables it - admin no longer needs proxy, disables it again - admin installs package that needs proxy Obviously, proxy should be enabled in the last step. So, having a wait to prevent modules from being autmatically enabled would be nice, but it would have to be an explicit setting and not the default behavior. I will mark this as wishlist. -- To UNSUBSCRIBE, email to debian-apache-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1403627.rHFUq0AuPt@k
Bug#719266: apache2_invoke enconf ignores dependencies disabled by admin
Package: apache2 Version: 2.4.6-2 If sysop disabled a module, then a maintainer script enable a module that depends on the first one, they are both enabled, ignoring admin choice. Example (from a fresh wheezy install upgraded to jessie): # a2enmod proxy Enabling module proxy. # a2dismod proxy Module proxy disabled. # a2query -m proxy No module matches proxy (disabled by site administrator) # APACHE2_MAINTSCRIPT_PACKAGE=testpkg # DPKG_MAINTSCRIPT_NAME=postinst # APACHE2_MAINTSCRIPT_NAME=postinst # APACHE2_MAINTSCRIPT_METHOD=configure # . /usr/share/apache2/apache2-maintscript-helper postint configure # apache2_invoke enmod proxy_http apache2_invoke: Enable module proxy_http # a2query -m proxy proxy (enabled by maintainer script) # grep Depends /etc/apache2/mods-available/proxy_http.load # Depends: proxy I expected apache2_invoke enmod proxy_http to fail since its dependency proxy module has been explicitly disabled by sysop. -- To UNSUBSCRIBE, email to debian-apache-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201308092153.05599.jmv_...@nirgal.com
