[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1074180: marked as done (transition: php8.4)

Your message dated Fri, 10 Jan 2025 10:42:08 +0100
with message-id <4139b33f-87d5-429e-9e54-5907793d6f2f@debian.org>
and subject line Re: [pkg-php-pear] Horde issues [Was: Bug#1074180: transition: php8.4]
has caused the Debian Bug report #1074180,
regarding transition: php8.4
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 owner@bugs.debian.org
immediately.)


-- 
1074180: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074180
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: release.debian.org
Severity: normal
User: release.debian.org@packages.debian.org
Usertags: transition
X-Debbugs-Cc: pkg-php-pear@lists.alioth.debian.org, team+debian-horde-team@tracker.debian.org

Hi,

this is the pre-announcement of the bi-annual transition from PHP 8.2 to PHP 8.4
that happens before the next stable release.

Currently, the first alpha release of PHP 8.4 is planned for July 2024:

https://wiki.php.net/todo/php84

I'll try to get this to experimental as soon as possible, but usually the
extensions start to catch up with the changes around the first Release Candidate
(end of September 2024).  This is also usually the time when then PHPAPI version
settles and will not change anymore.

My guess is that it would be reasonable for packagers of downstream packages to
start more serious testing around first Beta version.

I've tried to CC the PEAR and HORDE packagers, if you know of more people who
should be involved in the transition, please let them know.

Ondrej

Ben file:

title = "php8.4";
is_affected = .depends ~ /phpapi-/;
is_good = .depends ~ /phpapi-2024/;
is_bad = .depends ~ "phpapi-20220829";

--- End Message ---
--- Begin Message --- 
On 24/12/2024 08:35, Emilio Pozuelo Monfort wrote:

On 23/12/2024 15:30, David Prévot wrote:

Hi,

On 19/12/2024 09:30, Mike Gabriel wrote:

On  Do 19 Dez 2024 09:22:52 CET, David Prévot wrote:

On 16/12/2024 14:15, David Prévot wrote:
[…] It seems that most regressions are related to Horde (hence CCing the team and Mike) 

Half (14) of the 28 remaining issues spotted by debci are about Horde packages.

[…]
The Horde situation in Debian is quite sad. Upstream is working on some modernization aka Horde 6, but nothing in sight so far.
I'll ping Horde upstream on the current status the coming days, can you - for now - ignore the php-horde-* package in the onoing transition? 
If by ignoring, you mean “get it removed from testing”, I assume it’s possible.
Looking at what’s left on the [excuse] page, there are three end-user packages (mediawiki, phpldapadmin and phpmyadmin), all other look like libraries that are not used by any package currently in testing (well, except symfony, but the last upload is targeted to fix the remaining test issue on i386). 

     excuse: https://qa.debian.org/excuses.php?package=php-defaults
I have removed some of those packages (mostly horde and a couple others). However at least libphp-swiftmailer can't be removed currently. symfony depends on php-monolog which depends on libphp-swiftmailer.
Also there's a chain in php-opis-closure -> php-zumba-json-serializer -> phpmyadmin-sql-parser -> phpmyadmin.
So those need to be looked at, alongside the applications (mediawiki, phpmyadmin, etc).
Those got fixed, but php-defaults wasn't able to migrate, because php-common breaks php8.2-common. Marking php8.2 for removal didn't help, because then britney tried to remove all the php modules that still depended on php8.2 in testing (all of them).
In the end I used a force-hint to make php-defaults migrate, breaking php8.2, and removed it in a follow-up britney run. With that done, the transition is over. 

Cheers,
Emilio

--- End Message ---
Reply to: