Control: tags -1 moreinfo On 2023-11-12 21:42:20 +0100, Markus Blatt wrote: > Package: release.debian.org > Severity: normal > User: release.debian....@packages.debian.org > Usertags: transition > X-Debbugs-Cc: debian-scie...@lists.debian.org > > Dear Debian release team, > > A new upstream release of OPM is available. To ease migration to testing I am > requesting a mini-transition. Uploading to unstable would probably work even > without a transition, but I would like to play it safe. > > This should only affect the OPM source packages opm-common, opm-grid, opm- > models, opm-simulators and opm-upscaling. > > I have already uploaded new versions to experimental that seemed to have built > without any issues, see [1]. > (please explain about the transition: impacted packages, reason, ... > for more info see: https://wiki.debian.org/Teams/ReleaseTeam/Transitions) > > Ben file: > > title = "libopm-common-2023"; > is_affected = .depends ~ "libopm-common-2023.04" | .depends ~ "libopm- > common-2023.10"; > is_good = .depends ~ "libopm-common-2023.10"; > is_bad = .depends ~ "libopm-common-2023.04";
libopm-common has a Provides: libopm-common-X, but the shared library included in libopm-common also has a SONAME of libopm-common.X. Why is the packaging not following the common practice of matching the package name with the SONAME? Cheers -- Sebastian Ramacher
