Thursday, 21 October 2021

Re: PHP 8.1 transition plan

On Thu, Oct 21, 2021 at 12:03:58PM -0700, Steve Langasek wrote:
> Thanks, Bryce.
> On Thu, Oct 21, 2021 at 11:28:10AM -0700, Bryce Harrington wrote:
> > Hi devs,
> > I've started on the php 8.1 transition, details are here:
> >
> >
> > I anticipate this PHP update will be straightforward; the challenge will
> > be getting it completed prior to the OpenSSL 3.0 transition starting, as
> > the two certainly have potential for intertwining. The OpenSSL
> > transition starts the week of Nov 4th, so that gives 2 weeks, which is a
> > bit tight for transitioning php but potentially doable if no major
> > troubles crop up.
> The entanglement is expected to be minimal. If the transitions overlap, php
> does not have to be rebuilt against openssl 3 right away, and not doing so
> will not block migration of openssl 3 to the release pocket (because
> migrating it will not remove, or cause uninstallability of, the libssl1.1
> binary packages); and if php8.1 does end up built against openssl 3 (e.g.
> because php8.1 has to be reuploaded to fix a bug), we will hopefully not see
> openssl 3 blocking it in -proposed for too long (the longest delay with
> openssl 3 is likely to be resolving autopkgtest regressions in the
> reverse-dependencies, which may involve tracking down and ignoring test
> failures from packages that aren't yet ported to openssl 3).

Ah, that assessment is good to hear.

One other note is that our current php8.0 does not support OpenSSL 3.0,
but php8.1 does. However, there's a workaround patch for php8.0 if

> > The php8.1 language runtime itself has been uploaded to -proposed for
> > universe; it won't migrate to release until the full transition is
> > complete. php8.0 will remain in the archive until that point.
> I actually can't see any reason that it would block in -proposed for the
> transition as a whole, can you clarify?

Sorry, what I should have said is it won't move to *main* until the
transition is complete.

What's keeping it in -proposed presently is a build issue for armhf due
to a couple unsupported assembly calls (details in wiki).

> > I've updated php-defaults in -proposed to set 8.1 as the default. This
> > allows no-change rebuilds of various php components to build against
> > that version. This rebuilding of the PHP ecosystem is what consumes
> > most of the time for this transition, and of course help's always
> > welcome.
> php-defaults of course will block for a while :)
> Cheers,
> --
> Steve Langasek Give me a lever long enough and a Free OS
> Debian Developer to set it on, and I can move the world.
> Ubuntu Developer

> iQIzBAABCgAdFiEErEg/aN5yj0PyIC/KVo0w8yGyEz0FAmFxuZgACgkQVo0w8yGy
> Ez24IhAAhPc3rL5g316gStN67DrbPnkfuhRvBpdcsZzIoVkVvWv7EWL6PtSGBTUa
> tVAaaR1QU23L8H7vSOCayhdWumRSZuZhiNXGj+wm1KDv9HC1VyrocW0VJoSC/Nm/
> d2FWa9PFgNCaqju5TMmA0O7hOYH/uL0WWG6s6TTVf//upRp5Le0t2zha0kny6nuw
> xwq52gV9eEbzLS8nWjHRsefK2vmuFh4kcKQvU3TjIci6UCRPBKOApl1Ir81lsm7u
> mpzRVSjFcJgrn4vE7g8ELbMIPLCgx1bUduGbzjLQPMnolw9rKw1RhxxFx9rCX6l+
> BC1hHy3oKaYvbRSOsZxR96B4FnC7VgHtC2MZCitRLLdcstlfwH1ftHJ/fZQbq2kp
> W2I9x4MshBCv56fRs6jf2yDkHNqdoYrROmHYl8D5/N6O+gTvH+wu4PxWjvMCf2q5
> ZU1xt53uvQZZVycO0gazFx6Jj44PDdU1NznDrycfWJq4D+BIf7U5FnV3M91/WCc+
> d/KgtgzbulZHnp8oWUsq/CgHVN3bIC11/EvDxP0RFm4JF5HsQHVrsrt6hoT8w3ks
> xkdK3XUfQS/QniL+djPetZr2eYswvzTcxoi/v2XutsxG3HnhUUE=
> =qzOl

> --
> ubuntu-devel mailing list
> Modify settings or unsubscribe at:

ubuntu-devel mailing list
Modify settings or unsubscribe at: