Bug#1064146: Update snakeyaml to v2.2 or later
tony mancill
tmancill at debian.org
Tue Apr 15 17:33:37 BST 2025
On Tue, Apr 15, 2025 at 03:28:32PM +0200, Pierre Gruet wrote:
> > We probably also need to update reverse dependencies, e.g. testng[1]
> > and jtreg7[2]. I will try to look into it.
> >
> > Best Regards,
> > Vladimir.
> >
> > [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1102778
> > [2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1102767
>
> May I suggest that we instead downgrade the version of snakeyaml back to
> 1.33?
>
> Many RC bugs have been filled in (#1102778, #1102767, #1102764, #1102762
> just to name a few) after version 2.0+ds was uploaded, snakeyaml itself
> is not migrating because of failing autopkgtests in rdeps, and we are in
> Soft Freeze so I guess trying to fix all of these issues is not worth
> our time and is not "small, targeted fixes".
Since 2.0 introduces breaking API changes - see the "Backwards-incompatible"
changes in [1], I agree with Pierre that we should downgrade for Trixie.
I'm not sure how we should version it - perhaps: 2.0+ds+really1.33-1 ?
And then 2.0+ds+really2.0-1, or better yet skip 2.0 and upload 2.2+ds to
experimental, or wait until after the trixie release cycle.
Mechtilde, will you handle the upload?
Thank you,
tony
[1] https://bitbucket.org/snakeyaml/snakeyaml/wiki/Changes
More information about the pkg-java-maintainers
mailing list