PHP 8.0 transition plan

Sebastien Bacher seb128 at
Fri May 21 08:41:15 UTC 2021

Hey Bryce, thanks for the reply!

So it's a bit tricky. The new libsoup3 isn't out yet but even if it was,
the new version includes quite some refactoring and API changes so I'm
unsure if we will be able to transition the archive in a cycle or have 2
and 3 arounds for a while, which means we need to figure out what to do
with the current source.

The commit you mentioned basically removes public functions so is an
API/ABI incompatible change. Checking on those
functions have some users in the archive. Basically we would have to
change the soname in a distro specific way if we were to do that
properly but having a soname difference over upstream would make us
incompatible with existing binaries...

Would adding xmlrpc back on the php side temporarly until we get
libsoup3 and the archive transitioned to it be an option? If not I'm
unsure what's the best course of action...


Le 21/05/2021 à 01:08, Bryce Harrington a écrit :
> Looks like libsoup3 is beta (i.e. 2.99.5 released a couple weeks ago) so
> would it be worth looking at merging that from upstream?  If not,
> perhaps you could consider backporting the above commit to remove the
> xmlrpc support?

More information about the ubuntu-devel mailing list