ubuntustudio-bugs team mailing list archive

[Paride Legovini <1952918@xxxxxxxxxxxxxxxxxx>]

** Description changed:

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

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to fluidsynth in Ubuntu.
Matching subscriptions: Ubuntu Studio Bugs
https://bugs.launchpad.net/bugs/1952918

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

Status in fluidsynth package in Ubuntu:
  New

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