[Bug 1952918] [NEW] Please temporarely pull fluidsynth 2.2.4-2 from jammy-proposed

Paride Legovini 1952918 at bugs.launchpad.net
Wed Dec 1 12:42:35 UTC 2021


Public bug reported:

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 migrations 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.

** Affects: fluidsynth (Ubuntu)
     Importance: Undecided
         Status: New

** Description changed:

  fluidsynth 2.2.4-2 (currently in jammy-proposed) has a SONAME bump:
  
-   libfluidsynth2 -> libfluidsynth3
+   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)
+ $ 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)
+ $ comm -12 <(reverse-depends -b -l src:fluidsynth) <(reverse-depends -b -l src:liburing)
  mpd
  
  These other two migrations 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.

-- 
You received this bug notification because you are a member of Ubuntu
Package Archive Administrators, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1952918

Title:
  Please temporarely pull fluidsynth 2.2.4-2 from jammy-proposed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fluidsynth/+bug/1952918/+subscriptions




More information about the ubuntu-archive mailing list