Package: libapache2-mod-php4 Version: 4:4.3.10-8 Severity: critical Tags: patch Justification: breaks unrelated software
-- System Information: Debian Release: 3.1 APT prefers testing APT policy: (990, 'testing'), (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.10-1-k7-smp Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) Versions of packages libapache2-mod-php4 depends on: ii apache2 2.0.53-5 next generation, scalable, extenda ii apache2-mpm-prefork [apache 2.0.53-5 traditional model for Apache2 ii libbz2-1.0 1.0.2-5 high-quality block-sorting file co ii libc6 2.3.2.ds1-20 GNU C Library: Shared libraries an ii libcomerr2 1.35-6 The Common Error Description libra ii libdb4.2 4.2.52-18 Berkeley v4.2 Database Libraries [ ii libexpat1 1.95.8-1 XML parsing C library - runtime li ii libkrb53 1.3.6-1 MIT Kerberos runtime libraries ii libmagic1 4.12-1 File type determination library us ii libpcre3 4.5-1.1 Perl 5 Compatible Regular Expressi ii libssl0.9.7 0.9.7e-2 SSL shared libraries ii libzzip-0-12 0.12.83-4 library providing read access on Z ii mime-support 3.28-1 MIME files 'mime.types' & 'mailcap ii php4-common 4:4.3.10-8 Common files for packages built fr ii zlib1g 1:1.2.2-3 compression library - runtime -- no debconf information Dear valued maintainers, who`s "shocking new-new-new!" idea was it to compile libapache2-mod-php4 with --enable-experimental-zts // ==> "experimental" <==.. ;) as a STANDARD package for the majority of ALL debian users right now? Honestly? :) Quote: "Enable Zend Thread Safety for all SAPIs, meaning that our (!!!!!!!!!!!!!!!) modules are now compiled for ZTS APIs as well." And thats the point: Nearly ALL OTHER modules are NOT compiled with thread safety! Most, esp. including commercial modules, CANNOT be re-compiled due to lack of source code, e.g. Zend Performance Suite, IonCube and many many others.. Some will offer thread safe extensions in near future, some already do (you have to upgrade:$$$) and many do not. All these modules/extensions - over a sudden - do not work anymore. At least in our systems over here.. :) While it`s truly great, that debian aims to be leading the scene and people should be "happy" with the re-compiled modules supplied by you and therefore maybe even do not notice the current change, it is hard to believe that because of a small minority - that runs thread safe environments (i won't add any comments regarding the current "stability" of such here..) debian will FROM NOW ON FAIL AS A STANDARD with 90% of the modules out there and so in most cases only work with the ones supplied by debian. It`s not well balanced that EVERY single user, that just wishes to use an "additional/external" (means not debian supplied) module/extension, will have to RE-COMPiLE ALL PHP4 STUFF (base and over 20 modules) every single time, because a minority of excellent experienced and "1337" geeks. Please, please don`t forget about us! :-) I honestly do not only want to criticize - i have a simple suggestion: Why not split up and offer two packages - e.g. libapache2-mod-php4 (the "normal" one) and libapache2-mod-php4_ts (thread safe one)? Those companies that already do offer thread safe extensions for php split them up as well. Debian users could decide between both ways until thread safe environments will definitely take over (production systems) one day. Now, beat me up... :D Thank you very much! Kind Regards Alexander Schories Tuebingen, Germany If privacy or security of communication is on your mind, feel free to establish a secure transmission using the PGP public key obtainable from http://www.schories.com/alexander/pubkey/alexander_schories.asc -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
