Control: tags -1 + moreinfo On Sat, 2025-03-22 at 14:12 +0100, Sylvain Beucler wrote: > This is a request to RM the php-horde-* package set, from Debian 12 > bookworm specifically. > > Horde 5.x is currently incompatible with PHP8, making the package > mostly unusable, with many random errors. > See grave bugs at: > https://bugs.debian.org/cgi-bin/pkgreport.cgi?dist=stable;maint=team%2Bdebian-horde-team%40tracker.debian.org > > No complete patch set for these issues is currently available. > > New working installs are currently not possible, notably preventing > testing security fixes. > > Note: php-horde-* is already dropped from trixie. > Note: The maintainers wish to maintain it in unstable. > > See also the recap at: > https://lists.debian.org/debian-lts/2025/03/msg00012.html > and the maintainer's OK at: > https://lists.debian.org/debian-lts/2025/03/msg00017.html > > There are many packages, > `grep 'Package: php-horde' > deb.debian.org_debian_dists_bookworm_main_source_Sources` > gives me:
[A huge list] Our tooling assumes that a removal bug relates to a single source package. Someone will therefore need to ensure that bugs exist for all of the packages that are requested to be removed, and that they are tagged and titled appropriately (in the same way that an unstable removal report would be, not the incomplete format produced by reportbug, which we really should get fixed). ftp-master will also hate you unless we hack around the tooling, as dak will make them say "y<enter>" twice for each removal, interactively, during a point release :-p I'm tagging this moreinfo for now, as it's not currently actionable. I also don't understand why it's taken more than two years to reach this point, given that bookworm released with PHP 8.2, and that version was already in bookworm-as-testing since January 2023. According to the above, the package was already unsable _before_ the release, which was the appropriate time to have been trying to remove such a large package set. Regards, Adam
