Ok, removing fluidsynth from jammy-proposed for now, please be sure to
re-introduce it once the other transitions make it through.
I checked the rdeps of libfluidsynth3 from -proposed though, and it seems we
have two packages in jammy-proposed that have been rebuilt to now depend on
libfluidsynth3 instead of libfluidsynth2. I'm leaving them there as-is, but
it's good to know that those are already involved with the SONAME bump:
* mpd
* minuet
$ remove-package -s jammy-proposed -m "Temporarily dropping from -proposed to
let other transitions finish first. To be reintroduced (LP: #1952918)"
fluidsynth
Removing packages from jammy-proposed:
fluidsynth 2.2.4-2 in jammy
fluidsynth 2.2.4-2 in jammy amd64
fluidsynth 2.2.4-2 in jammy arm64
fluidsynth 2.2.4-2 in jammy armhf
fluidsynth 2.2.4-2 in jammy i386
fluidsynth 2.2.4-2 in jammy ppc64el
fluidsynth 2.2.4-2 in jammy riscv64
fluidsynth 2.2.4-2 in jammy s390x
libfluidsynth-dev 2.2.4-2 in jammy amd64
libfluidsynth-dev 2.2.4-2 in jammy arm64
libfluidsynth-dev 2.2.4-2 in jammy armhf
libfluidsynth-dev 2.2.4-2 in jammy i386
libfluidsynth-dev 2.2.4-2 in jammy ppc64el
libfluidsynth-dev 2.2.4-2 in jammy riscv64
libfluidsynth-dev 2.2.4-2 in jammy s390x
libfluidsynth3 2.2.4-2 in jammy amd64
libfluidsynth3 2.2.4-2 in jammy arm64
libfluidsynth3 2.2.4-2 in jammy armhf
libfluidsynth3 2.2.4-2 in jammy i386
libfluidsynth3 2.2.4-2 in jammy ppc64el
libfluidsynth3 2.2.4-2 in jammy riscv64
libfluidsynth3 2.2.4-2 in jammy s390x
Comment: Temporarily dropping from -proposed to let other transitions finish
first. To be reintroduced (LP: #1952918)
Remove [y|N]? y
1 package successfully removed.
** Changed in: fluidsynth (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to fluidsynth in Ubuntu.
https://bugs.launchpad.net/bugs/1952918
Title:
Please temporarely pull fluidsynth 2.2.4-2 from jammy-proposed
Status in fluidsynth package in Ubuntu:
Fix Released
Bug description:
fluidsynth 2.2.4-2 (currently in jammy-proposed) has a SONAME bump:
libfluidsynth2 -> libfluidsynth3
which is a fairly large transition:
$ reverse-depends -b -l src:fluidsynth | wc -l
30
This list of reverse-dependencies has exactly one package in common
with other two currently ongoing transitions:
$ comm -12 <(reverse-depends -b -l src:fluidsynth) <(reverse-depends -b -l
src:libidn)
vlc
$ comm -12 <(reverse-depends -b -l src:fluidsynth) <(reverse-depends -b -l
src:liburing)
mpd
These other two transitions are almost done, hopefully just requiring
couple of minor uploads (merging a new Debian revision of ghostscript
and uploading a new Ubuntu revision of exim4 to resolve a components-
mismatch).
I think it it would be better to finish these other two transitions
first, without fluidsynth, and then sync fluidsynth again, to be
handled separately.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fluidsynth/+bug/1952918/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
