On Fri, 2022-01-21 at 10:06 +0100, Markus Blatt wrote: > I assume that this version dependency was added when the packages > were built some time ago. Correct, see the dh_shlibdeps, dpkg-shlibdeps, deb-shlibs, deb-symbols and dpkg-gensymbols manual pages for details. > What is the recommend way to resolve this? In addition to the unsatisfiable dependency, the binaries in unstable haven't been built on a buildd, so they won't be accepted into testing. https://qa.debian.org/excuses.php?package=opm-common Rebuilding the package (either via a package update or a binNMU) will rebuild the binary, which will pick up the new libfmt dependency. If you elect for a binNMU that will solve the buildd binaries issue. If you elect for a package update, you just need to ensure your sponsor does a source-only upload so builds will happen on built on buildds. https://wiki.debian.org/binNMU https://wiki.debian.org/SourceOnlyUpload -- bye, pabs https://wiki.debian.org/PaulWise
Attachment:
signature.asc
Description: This is a digitally signed message part