Your message dated Thu, 09 Apr 2015 17:08:20 +0200 with message-id <1428592100.1278507.251295613.4003c...@webmail.messagingengine.com> and subject line has caused the Debian Bug report #712509, regarding php-common: disabled modules are auto-re-enabled on upgrade to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 712509: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=712509 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: php-common Version: 5.4.4-14+deb7u2 Severity: important Hi. Marking this as important, as it might have even security implications (e.g. when a module was intentionally. btw: I just thought I'd have reported this before, but couldn't find it in the open bugs... so please don't be annoyed if it's a duplicate ;) We have this nice mechanisms of module config files symlinked in: /etc/php5/conf.d/ (and also, well at least per default, the SAPI dirs which contains symlinks to l /etc/php5/conf.d as well). People may use different PHP configs for different PHP programs, e.g. via setting PHP_INI_SCAN_DIR. So they may want to enable some modules only in these locations, e.g. because they know they'll be anyway only used from SSL client auth secured connections... Therefore... a) I generally think, that modules shouldn't be auto-enabled there (I mean even on the first install). You have the nice php5dismod/php5enmod and everyone should be able to call them if he wants to. b) If one has removed such a symlink... (either by php5dismod or manually by rm)... it should NOT be auto-recreated on package upgrade... especially as this happens without any notice. Admittedly I'm not sure how to actually do (b) as these are not conffiles... but (a) would solve (b) as well ;-) Cheers, Chris.
--- End Message ---
--- Begin Message ---Version: 5.5.0+dfsg-7 php5 (5.5.0+dfsg-7) unstable; urgency=low [ Ondřej Surý ] * This release introduces several major packaging changes: + php5{en,dis}mod now accepts -s <SAPI> argument to selectively enable/disable module for specific SAPI; The -s also accepts ALL as an argument (Closes: #505743) + php5{en,dis}mod now records a state for a module and has two modi operandi: local administrator and maintainer script This has been lousely modeled after apache2 packaging scripts. Thanks Arno Töll for his work on dh_apache2, I have used some parts of it. + Packages can now depend on dh_php5 (provided by php5-dev) which provides: dh_php5, dh_phpize and dh_phpize_clean (also with dh integration). See php-apcu for an example how to build an PHP 5 extension now. The scripts definitely needs some improvements since I can't read nor write perl code without getting dizzy. + There's a new php5query script (again lousely modeled after Apache 2 a2query script) which you can use to query status of module (-m) and/or SAPI (-s) and also to list modules (-M) and SAPIs (-S). + This still needs more documentation and less ducktape. Contributions are welcome and to be discussed in pkg-php-maint mailing list first. -- Ondřej Surý <[email protected]> Tue, 09 Jul 2013 11:37:57 +0200 -- Ondřej Surý <[email protected]> Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server
--- End Message ---
