Bug#1127052: transition: dune-common (Mini-transition DUNE)

Markus Blatt markus at dr-blatt.de
Thu Feb 5 17:22:57 GMT 2026


Package: release.debian.org
Severity: normal
User: release.debian.org at packages.debian.org
Usertags: transition
X-Debbugs-Cc: dune-common at packages.debian.org, debian-science at lists.debian.org
Control: affects -1 + src:dune-common

Dear Debian release team,

A new upstream release of DUNE 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 dune-* and opm-* source packages dune-geometry,
dune-grid
dune-uggrid, dune-localfunctions, dune-typetree, dune-grid-glue, dune-
functions,
opm-common, opm-grid, opm-simulators and opm-upscaling. I am maintaining all of
those.

I have already uploaded new versions of the dune-* packages to experimental
that seemed
to have built without any issues and are all marked for migration, see [1]. On
my system
I was able to build the opm-* packages in a chroot using the dune-* packages
without
problems and only had to patch opm-simulators

Note the package is currently not following the common practice of matching the
package name
with the SONAME as upstream does not care about API changes and always changes
the SONAME for
every release. Also see [2]

Ben file:

title = "dune-common";
is_affected = .depends ~ "libdune-common-2.10.0" | .depends ~ "libdune-
common-2.11.0";
is_good = .depends ~ "libdune-common-2.11.0";
is_bad = .depends ~ "libdune-common-2.10.0";
notes = "https://lists.debian.org/debian-science/2023/01/msg00001.html";;
export = false;

Best,

Markus Blatt

[1] https://qa.debian.org/developer.php?login=markus%40dr-blatt.de
[2] https://lists.debian.org/debian-science/2023/01/msg00001.html



More information about the debian-science-maintainers mailing list