Bug#656486: Fwd: Suhosin with PHP 5.4 (debian #656486)

2012-01-26 Thread Lior Kaplan
Forwarding a replay I got from the author of Suhosin.

We'll wait for a new upstream release.

-- Forwarded message --
From: Stefan Esser stefan.es...@sektioneins.de
Date: Thu, Jan 26, 2012 at 9:22 AM
Subject: Re: Suhosin with PHP 5.4 (debian #656486)
To: Lior Kaplan kap...@debian.org


Hi,

PHP 5.4 is a release candidate only. They have to rerelease RC after RC
because new and new critical bugs pop up.
Also it is a new major version, which means the PHP developers break binary
compatibility.

This means it is unsafe to run Suhosin with PHP 5.4 even after having fixed
a few compile errors.

It needs to be checked that all functionality used by Suhosin did not
change internally. This will be done in time for the PHP 5.4 release, but
not now about a month before the actually planned official release.

Regards,
Stefan Esser


Bug#656486: Fwd: Suhosin with PHP 5.4 (debian #656486)

2012-01-26 Thread Jan Wagner
Hi Lior,

On Thursday, 26. January 2012, Lior Kaplan wrote:
 Forwarding a replay I got from the author of Suhosin.
 
 We'll wait for a new upstream release.
 
 -- Forwarded message --
 From: Stefan Esser stefan.es...@sektioneins.de
 Date: Thu, Jan 26, 2012 at 9:22 AM
 Subject: Re: Suhosin with PHP 5.4 (debian #656486)
 To: Lior Kaplan kap...@debian.org
 
 
 Hi,
 
 PHP 5.4 is a release candidate only. They have to rerelease RC after RC
 because new and new critical bugs pop up.
 Also it is a new major version, which means the PHP developers break binary
 compatibility.
 
 This means it is unsafe to run Suhosin with PHP 5.4 even after having fixed
 a few compile errors.
 
 It needs to be checked that all functionality used by Suhosin did not
 change internally. This will be done in time for the PHP 5.4 release, but
 not now about a month before the actually planned official release.

I was also in contact with the author about this issue, giving me the same 
informations. As the mail was encrytped I did not publish these. But I'm aware 
of the issue and keeping an eye on the commit log on github. ;)

With kind regards, Jan.
-- 
Never write mail to w...@spamfalle.info, you have been warned!
-BEGIN GEEK CODE BLOCK-
Version: 3.12
GIT d-- s+: a C+++ UL P+ L+++ E--- W+++ N+++ o++ K++ w--- O M V- PS PE Y++
PGP++ t-- 5 X R tv- b+ DI D+ G++ e++ h r+++ y 
--END GEEK CODE BLOCK--


signature.asc
Description: This is a digitally signed message part.