[php-maint] PHP 5.2.8 in Lenny
olivier.bonvalet at daevel.fr
Sun Jan 11 01:29:03 UTC 2009
mmm excuse me, but maybe should I submit directly 2 "dpatch" for the
debian's package ?
Olivier Bonvalet a écrit :
> Hello Sean,
> thanks for your answer, I understand the Debian's position but it's
> annoying for me ;) (our framework crash PHP at each page on Debian
> So I found the 2 PHP bugs which concern us, and was fixed by PHP 5.2.7
> (yes, 5.2.7) :
> - http://bugs.php.net/bug.php?id=46157 :
> It's a small PDO bug, which is not present on Debian Etch. The
> patch is really short :
> -http://bugs.php.net/bug.php?id=46308 :
> A memory corruption problem. It seems the bug is present on Etch,
> but we crash PHP really really less often.
> I ask on the php-dev mailing list, and it seems the relative patch
> is this one :
> I hope this will help. I will file a bug in the Debian BTS, but...
> there is not a "simple" web form to do that !?
> Thanks again,
> sean finney a écrit :
>> salut olivier,
>> On Wed, Jan 07, 2009 at 11:22:08PM +0100, Olivier Bonvalet wrote:
>>> I would like to know if there is a problem with the integration of
>>> PHP 5.2.8 in Lenny : we have some memory corruption problems with
>>> the 5.2.6 version ( which produce "segmentation faults" and "canari
>>> free warnings", cf this bug http://bugs.php.net/bug.php?id=46308 ).
>> i find it highly doubtful that 5.2.8 will make it into lenny. 5.2.8 was
>> an emergency point release issued one day after 5.2.7 was released,
>> due to
>> a regression caused in the mix of fixes and features in that new
>> release. this is pretty common for php releases and why we usually
>> wait a bit after a new release before uploading to debian. also,
>> because of such an
>> unhealthy mix, we can't make an upload targeted for lenny with such an
>> expectation for further regressions.
>>> So on the developpement servers we use a recompiled package, between
>>> the 5.2.6 and 5.2.7. But Lenny is freezed to become the new "debian
>>> stable release", no ? I hope PHP 5.2.6 will not be on the future
>>> "debian stable", otherwise we will have a lot of problems on
>>> production servers.
>>> But maybe I can help for something ?
>> if you're experiencing the bug above, the best course of action i can
>> is to see if you can find the fix for the above bug on cvs.php.net
>> (they have
>> a commits mailing list which might help). if you can find the fix,
>> it's much
>> more likely that we can include this patch in an upload targeted for
>> otherwise, you could wait for a backport to show up, but you won't
>> likely see
>> that until some time after lenny releases.
>> in any case you should also file a bug in the debian BTS about this
>> problem so
>> that it is documented and tracked.
More information about the pkg-php-maint