Your message dated Mon, 21 Sep 2026 21:16:07 -0300
with message-id <[email protected]>
and subject line Re: libphp-simplepie: Debian specific changes break wordpress
has caused the Debian Bug report #669054,
regarding libphp-simplepie: Debian specific changes break wordpress
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
669054: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=669054
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: libphp-simplepie
Version: 1.2.1-3
Severity: important
The changes made in response to #651515 break WordPress. It's good to
clean up code but this should be upstream's responsibilities and deviating
from upstream can cause issues with external code using simplepie.
In this case, wordpress redefines a method of simplepie and that method
has been changed to "static" by Thorsten's patch (I don't know why) and
it now fails with this:
PHP Fatal error: Cannot make static method SimplePie_Cache::create() non
static in class WP_Feed_Cache in
/usr/share/wordpress/wp-includes/class-feed.php on line 6
The code in question seems legitimate:
class WP_Feed_Cache extends SimplePie_Cache {
/**
* Create a new SimplePie_Cache object
*
* @static
* @access public
*/
function create($location, $filename, $extension) {
return new WP_Feed_Cache_Transient($location, $filename,
$extension);
}
}
I would thus kindly ask you to revert that change at least partially
for all the methods that have been marked static and let upstream deal
properly with the fallout of the incompatible change...
Cheers,
-- System Information:
Debian Release: wheezy/sid
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500,
'unstable'), (500, 'testing'), (500, 'stable'), (150, 'experimental')
Architecture: i386 (x86_64)
Kernel: Linux 3.2.0-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages libphp-simplepie depends on:
ii php5-cli 5.4.1~rc1-1
ii php5-curl 5.4.1~rc1-1
ii php5-intl 5.4.1~rc1-1
libphp-simplepie recommends no packages.
libphp-simplepie suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 1.3.1+dfsg-1
Hi,
closing this one for the record. The breakage came from the Debian
patch
assigning_the_return_value_of_new_by_reference_is_now_deprecated.patch,
added in 1.2.1-3 for #651515, which turned SimplePie_Cache::create()
and a few other methods into static ones. That patch was dropped with
the 1.3.1+dfsg-1 upload in November 2014, so the package has matched
upstream's method signatures since then; the changelog entry just did
not reference this bug.
Nothing in the current packaging changes signatures either: the
remaining patches only set the default cache directory and make the
compiled file reproducible. Upstream 1.9.0 still has create() as an
instance method, with a separate static get_handler(), so there is no
divergence left to coordinate. wordpress no longer uses
libphp-simplepie in Debian, and fusionforge is not in the archive
anymore.
Cheers
signature.asc
Description: This is a digitally signed message part
--- End Message ---
