Since etch php is compiled with large file support. This breakes binary compatibility to other packages, which are commonly not compiled with LFS and leads into trouble with 3rd party extensions, cause these are precompiled against the ABI of upstream and LFS not turned on. One example is Zend Optimizer. You may say this will only hit closed source applications, but if these are customer requirements, you have to solve the issue in some way.
You can do this by compiling your php and all extension from source without LFS enabled, but here you have to care about bugs, regressions and exploits for your own.
An other solution is to rebuild the packages from etch with LFS disabled. I’ve done this with the source packages of php4 and php5 from etch. Additionaly I did backport php-suhosin from unstable against this php packages for php4 and php5.
Packages are available at http://ftp.cyconet.org/debian/archive/special/ or via
deb http://ftp.cyconet.org/debian etch-special-cyconet main non-free contrib
If there are any DSA popping up, you can expect updates with a short delay. Please keep in mind, that you cant install php extension directly from etch. You need to rebuild them against php[45]-dev with disabled LFS. Other php packages may apear later.
Update: We migrated a customer system with Zend Optimizer to etch. To my suprise, it was working with latest version of Zend Optimizer out of the box with php4. Can’t say anything for php5, cause there are some modifications needed, until the applications are working with php5.
Maybe anybody can verify this with php5?
Until all works well with stock php[45], I wont maintain the packages mentioned above.
Since one week eGroupware 1.4RC1 is available. Peter did upload it into experimental and I did repackage it for etch, for a smarty integration (dpkg -i for > 15 packages sucks).
You can download it by using the following line in sources.list:
deb ftp://ftp.cyconet.org/debian etch-backports main non-free contrib
Please note that you also need installed egroupware-egw-pear.
If you experience troubles, report your bugs upstream.
I did rebuild the brand new version of wordpress for etch. New user requests and etch-bpo stated:
* Is the backport neccessary? I don’t think we should upload packages to bpo
simply because we can do it if you can install the package directly from
testing without any recompilation we shouldn’t add it to bpo. Pinning
exists.
So I’m not allowed to upload it to backports.org, but I did upload it to my repro, like the following other packages:
- backuppc
- collectd (from experimental)
- fuzzyocr3 (from experimental)
- gallery2
- libfile-rsyncp-perl
- php-suhosin
- xen-shell
You can download it by using the following line in sources.list:
deb ftp://ftp.cyconet.org/debian etch-backports main non-free contrib
I’m stuck of the requests linking php5 on backports.org against “MySQL5″.
You need support of MySQL5 or the mysqli extention for your php5 packages for sarge? So the packages on backports.org are not what you want.
The packages are compiled against libmysqlclient12 (mysql 4.0) cause all apache modules (on backports.org) are compiled against this version. Linking php5 against an other version will lead you in trouble when using these apache modules and php5 together, cause sarge doesn’t support “versioned symbols”.
For more information see the threads on php-maint or
backports-users! If you install packages from backports.org, you should read the latter one anyways.
