Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition
X-Debbugs-Cc: symf...@packages.debian.org, pkg-php-p...@lists.alioth.debian.org
Control: affects -1 + src:symfony
Control: block -1 by 1039731 1039732 1039733 1039734 1039735
Hi,
We’d like to prepare the symfony transition. It’s building over a
hundred arch:all binary packages, that are (in)directly used by a few
hundred other arch:all packages. Given the increased number of related
packages, and because the last symfony 5 transition was not as smooth as
previous ones, we’re opening a bug even if no package builds need to be
handled by the Release Team (but maybe some removals may help at some
point).
The experimental pseudo-excuse page is unfortunately not very
informative about the amount of breakages we could expect, so Athos
rebuilt reverse build-dependencies with mass-rebuild. Yet this doesn’t
catch uninstallable packages, e.g., phpmyadmin and php-laravel-framework
in their current state, depending on php-symfony-$stuff (<< 6~~).
https://qa.debian.org/excuses.php?experimental=1=symfony
https://people.ubuntu.com/~athos-ribeiro/rebuilds/symfony6/index.html
Do you have a way to spot packages in Sid currently depending on
symfony (<< 6~) in order to file bugs and eventually provide patches?
I hope we can have soon enough a view of the amount of breakage in order
to hopefully kick this transition during DebCamp…
Regards
David
signature.asc
Description: PGP signature
