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?
Attachment:
signature.asc
Description: This is a digitally signed message part.