Comment 2 for bug 1983205

Hi Kraut,

Thanks for taking the time to report this bug.

After reading
https://github.com/php/php-src/issues/8164,
it seems that we do not currently have a straightforward reproducer for the bug. Would you be able to provide one? This would be quite helpful here when it comes to uploading a fix for the issue (keep reading below).

In Ubuntu stable releases, we usually apply patches following the SRU process
(see https://wiki.ubuntu.com/StableReleaseUpdates#SRU_Bug_Template)
instead of updating software to newer versions. There are exceptions to this process, which are documented in https://wiki.ubuntu.com/StableReleaseUpdates#Documentation_for_Special_Cases, but PHP is currently not part of those exceptions.

Circling back to the linked github issue, it seems that
https://github.com/php/php-src/pull/8297
was the fix that closed that issue. Therefore, applying that patch should hopefully fix the issue you have been experiencing.

For kinetic (currently development release) I'd rather merge Debian's PHP 8.1.7, which should contain the fix. I will start working on this merge soon.

Now for jammy, while the upstream bug and the drupal bug could not provide a reliable, minimal reproducer [1], it would be nice if we could find one so we are able to confirm that that one specific patch is indeed the fix for this issue. Once again, would you be able to provide one while I work on the fix for kinetic? If not, I will get to that after I am done working on the kinetic merge.

[1]:
"""
Steps to reproduce

There are no obvious steps to reproduce, you need a module installed which triggers a PHP deprecation notice, possibly php-fpm, and it may take several days for this error to appear.
"""