On 22. 11. 2021, at 14:15, David Pr=C3=A9vot <david@tilapin.org> =
wrote:
=20
Le 22/11/2021 =C3=A0 08:45, Ond=C5=99ej Sur=C3=BD a =C3=A9crit :
=20
> Or we could stop delaying the inevitable[1] and instead of bumping
> epoch just go ahead with the transition.
=20
You don=E2=80=99t need to bump epoch (especially on source package and =
every binary ones) just to temporarily bump version of one binary =
package.
=20
IIRC, last time such transition was pushed in an uncoordinated way =
like this (7.3 -> 7.4), it took months to handle. Can we please not =
repeat this painful experience for such an expected bigger transition =
(7.4 -> 8.1)?
You asked for more time last December, a year has passed and it=E2=80=99s =
again not good time. What would just having more time grant? We cannot =
have bookworm released with PHP 7.4, so what will change and how much =
more time will be =E2=80=9Cenough=E2=80=9D? We cannot hold back on PHP =
version because Debian contains software that cannot keep up with the =
PHP release model. People would actually appreciate having a recent PHP =
interpreter packaged in Debian instead of software written in PHP. As =
far as I understand most people are using stuff like composer anyway.
The current status is holding some of us to actually work on this =
transition (e.g., I=E2=80=99m not able to properly build and push new =
versions expected to actually work with recent PHP, and have little view =
of the remaining issues that could be spotted via autopkgtests in =
experimental, since little or no bugs were raised on affected packages).
What transition? PHP 7.4 has been released in Debian bullseye, so I =
cannot imaging what transition you are talking about. PHP 7.4 is =
switching to security-only in December with only one extra year. We need =
to switch to PHP 8.1 now and to PHP 8.2 before bookworm release.
So, again - how much time would be enough if a year was not enough?
Ondrej