Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Bug#1041982: transition: symfony 6
2 views
Skip to first unread message
David Prévot
Jul 25, 2023, 8:00:04 AM7/25/23
to
Package: release.debian.org
Severity: normal
User: release.d...@packages.debian.org
Usertags: transition
X-Debbugs-Cc: sym...@packages.debian.org, pkg-ph...@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&package=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
Severity: normal
User: release.d...@packages.debian.org
Usertags: transition
X-Debbugs-Cc: sym...@packages.debian.org, pkg-ph...@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&package=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
Graham Inggs
Aug 26, 2023, 1:10:03 PM8/26/23
to
Hi David
On Tue, 25 Jul 2023 at 11:57, David Prévot <taf...@debian.org> wrote:
> Do you have a way to spot packages in Sid currently depending on
> symfony (<< 6~) in order to file bugs and eventually provide patches?
You could use a ben tracker for this.
I've set up something basic [1].
Feel free to submit MRs in Salsa [2] with improvements.
Regards
Graham
[1] https://release.debian.org/transitions/html/symfony6.html
[2] https://salsa.debian.org/release-team/transition-data
On Tue, 25 Jul 2023 at 11:57, David Prévot <taf...@debian.org> wrote:
> 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've set up something basic [1].
Feel free to submit MRs in Salsa [2] with improvements.
Regards
Graham
[1] https://release.debian.org/transitions/html/symfony6.html
[2] https://salsa.debian.org/release-team/transition-data
David Prévot
Sep 17, 2023, 10:40:04 AM9/17/23
to
Hi,
> Le 24/06/2023 à 01:29, William Desportes a écrit :
[…]
> Great, #1041982 does not have much blockers anymore, maybe we can schedule
> the transition then.
FYI, we had a workshop during DebConf with Athos in order to try and
determine what other packages (and relevant blockers) need to be
uploaded from experimental to unstable in order to perform this
transition.
So far, only the four following versioned packages have been determined
as needed in sync with Symfony.
php-symfony-contracts (>= 3)
php-psr-cache (>= 3)
php-psr-container (>= 2)
php-psr-log (>=3)
That led us to notice other packages will become uninstallable (due to
the version constraints), or simply broken. A few more bugs have been
open in this regard (blocking this transition bug), but roughly, the
following end user packages (families) are not yet ready.
civicrm (#1051988)
kanboard (#1051989 and php-pimple)
Laravel (#1051985 and #1039731, and php-faker)
shaarli (#1039733 and php-slim, php-pimple)
civicrm is not in stable (only recently migrated again to testing after
a php-log fix, Dmitry CCed anyway). Laravel was removed from testing
during the previous symfony 5 transition, Robin already explicitly
agreed that can be Laravel can be removed again from testing until a new
upstream version is packaged.
I don’t know if there are strong opinions about kanboard and shaarli,
Joseph and James CCed.
Some bugs are still to be filled (e.g., php-faker, php-slim, and
php-pimple), but it may already be time to raise the severity of the
blocking bugs.
Regards,
taffit
P.-S.: Pad used to track issues during DebConf.
https://pad.dc23.debconf.org/p/symfony6
Athos may try to rebuild packages also depending on recent version of
php-symfony-contracts, php-psr-cache, php-psr-container and php-psr-log
in order to figure out if more package are affected by this transition.
> Le 24/06/2023 à 01:29, William Desportes a écrit :
[…]
> Great, #1041982 does not have much blockers anymore, maybe we can schedule
> the transition then.
FYI, we had a workshop during DebConf with Athos in order to try and
determine what other packages (and relevant blockers) need to be
uploaded from experimental to unstable in order to perform this
transition.
So far, only the four following versioned packages have been determined
as needed in sync with Symfony.
php-symfony-contracts (>= 3)
php-psr-cache (>= 3)
php-psr-container (>= 2)
php-psr-log (>=3)
That led us to notice other packages will become uninstallable (due to
the version constraints), or simply broken. A few more bugs have been
open in this regard (blocking this transition bug), but roughly, the
following end user packages (families) are not yet ready.
civicrm (#1051988)
kanboard (#1051989 and php-pimple)
Laravel (#1051985 and #1039731, and php-faker)
shaarli (#1039733 and php-slim, php-pimple)
civicrm is not in stable (only recently migrated again to testing after
a php-log fix, Dmitry CCed anyway). Laravel was removed from testing
during the previous symfony 5 transition, Robin already explicitly
agreed that can be Laravel can be removed again from testing until a new
upstream version is packaged.
I don’t know if there are strong opinions about kanboard and shaarli,
Joseph and James CCed.
Some bugs are still to be filled (e.g., php-faker, php-slim, and
php-pimple), but it may already be time to raise the severity of the
blocking bugs.
Regards,
taffit
P.-S.: Pad used to track issues during DebConf.
https://pad.dc23.debconf.org/p/symfony6
Athos may try to rebuild packages also depending on recent version of
php-symfony-contracts, php-psr-cache, php-psr-container and php-psr-log
in order to figure out if more package are affected by this transition.
David Prévot
Jan 3, 2024, 1:10:04 PM1/3/24
to
control: block -1 with 1051989
control: severity 1051989 important
control: severity 1051988 important
Le Sun, Sep 17, 2023 at 07:57:03PM +0530, David Prévot a écrit :
> […] roughly, the
#1051989).
> […] it may already be time to raise the severity of the
> blocking bugs.
I’m in favour of raising the severity of bugs blocking this transition
to RC level ASAP: Symfony 6 has been in experimental for a while now,
and it’s the targeted version for Trixie anyway (6.4 is likely to be the
latest LTS version available before the Freeze, while 5.4 will be EOL
soon after Trixie gets released).
https://symfony.com/releases#symfony-releases-calendar
> Athos may try to rebuild packages also depending on recent version of
> php-symfony-contracts, php-psr-cache, php-psr-container and php-psr-log
> in order to figure out if more package are affected by this transition.
That would still be very much welcome if time permits, but IMHO not a
blocker (we used to handle such transition without involving the release
team nor as much build testing than already done for this transition.
Thanks to all people involved, the current state makes us in a better
position to move forward).
Regards,
taffit
control: severity 1051989 important
control: severity 1051988 important
Le Sun, Sep 17, 2023 at 07:57:03PM +0530, David Prévot a écrit :
> […] roughly, the
> following end user packages (families) are not yet ready.
>
> civicrm (#1051988)
> kanboard (#1051989 and php-pimple)
> Laravel (#1051985 and #1039731, and php-faker)
> shaarli (#1039733 and php-slim, php-pimple)
>
> civicrm is not in stable […] Robin already explicitly
>
> civicrm (#1051988)
> kanboard (#1051989 and php-pimple)
> Laravel (#1051985 and #1039731, and php-faker)
> shaarli (#1039733 and php-slim, php-pimple)
>
> agreed that can be Laravel can be removed again from testing until a new
> upstream version is packaged.
>
> I don’t know if there are strong opinions about kanboard and shaarli,
> Joseph and James CCed.
kanboard has been removed from testing in the mean time (due to
> upstream version is packaged.
>
> I don’t know if there are strong opinions about kanboard and shaarli,
> Joseph and James CCed.
#1051989).
> […] it may already be time to raise the severity of the
> blocking bugs.
I’m in favour of raising the severity of bugs blocking this transition
to RC level ASAP: Symfony 6 has been in experimental for a while now,
and it’s the targeted version for Trixie anyway (6.4 is likely to be the
latest LTS version available before the Freeze, while 5.4 will be EOL
soon after Trixie gets released).
https://symfony.com/releases#symfony-releases-calendar
> Athos may try to rebuild packages also depending on recent version of
> php-symfony-contracts, php-psr-cache, php-psr-container and php-psr-log
> in order to figure out if more package are affected by this transition.
blocker (we used to handle such transition without involving the release
team nor as much build testing than already done for this transition.
Thanks to all people involved, the current state makes us in a better
position to move forward).
Regards,
taffit
Debian Bug Tracking System
Jan 3, 2024, 1:10:04 PM1/3/24
to
Processing control commands:
> block -1 with 1051989
Bug #1041982 [release.debian.org] transition: symfony 6
1041982 was blocked by: 1051988 1051985 1039733 1039732 1039734 1039735 1039731
1041982 was not blocking any bugs.
Added blocking bug(s) of 1041982: 1051989
> severity 1051989 important
Bug #1051989 [kanboard] kanboard: FTBFS with php-psr-log >= 3, needed for the symfony 6 transition
Severity set to 'important' from 'normal'
> severity 1051988 important
Bug #1051988 [civicrm-common] civicrm-common: Not compatible with symfony 6
Severity set to 'important' from 'normal'
--
1041982: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041982
1051988: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051988
1051989: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051989
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
> block -1 with 1051989
Bug #1041982 [release.debian.org] transition: symfony 6
1041982 was blocked by: 1051988 1051985 1039733 1039732 1039734 1039735 1039731
1041982 was not blocking any bugs.
Added blocking bug(s) of 1041982: 1051989
> severity 1051989 important
Bug #1051989 [kanboard] kanboard: FTBFS with php-psr-log >= 3, needed for the symfony 6 transition
Severity set to 'important' from 'normal'
> severity 1051988 important
Bug #1051988 [civicrm-common] civicrm-common: Not compatible with symfony 6
Severity set to 'important' from 'normal'
--
1041982: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041982
1051988: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051988
1051989: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051989
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
David Prévot
Feb 21, 2024, 2:30:04 AM2/21/24
to
Hi,
Le Wed, Jan 03, 2024 at 07:04:12PM +0100, David Prévot a écrit :
[…]
experimental during the latest Debian Reunion Hamburg, and I wish to
proceed with the transition during the next MiniDebCampHamburg happening
early March (in less than two weeks).
https://wiki.debian.org/DebianEvents/de/2024/MiniDebCampHamburg
This transition should not interfere with any other one, and should not
even need any help from the Release Team (no binNMU since they’re all
arch:all packages), yet they were helpful last time to speed it up by
removing blocking packages from testing because we didn’t raise the
blocking bug severity early enough.
Regards,
taffit
Le Wed, Jan 03, 2024 at 07:04:12PM +0100, David Prévot a écrit :
[…]
> I’m in favour of raising the severity of bugs blocking this transition
> to RC level ASAP: Symfony 6 has been in experimental for a while now
I intend to do so early next week: symfony 6 was introduced in
> to RC level ASAP: Symfony 6 has been in experimental for a while now
experimental during the latest Debian Reunion Hamburg, and I wish to
proceed with the transition during the next MiniDebCampHamburg happening
early March (in less than two weeks).
https://wiki.debian.org/DebianEvents/de/2024/MiniDebCampHamburg
This transition should not interfere with any other one, and should not
even need any help from the Release Team (no binNMU since they’re all
arch:all packages), yet they were helpful last time to speed it up by
removing blocking packages from testing because we didn’t raise the
blocking bug severity early enough.
Regards,
taffit
0 new messages