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
-----BEGIN PGP SIGNATURE-----
iQIzBAABCgAdFiEEYQsotVz8/kXqG1Y7MRa6Xp/6aaMFAmHrT1QACgkQMRa6Xp/6 aaMaUw/6A8EqPoZMPtkl53lsS8p4g8dD1nbSjHZatr8eMDEnPUOKQkXZS0GHi2Hx DbIr2x9T9vJa77HRVrjdr4679ALIoGB8wszgMhn5HZKLVFH+y69YgMPNnrZe5Cw+ KQjy0BcZDMoHlPoNNbCLHf7cPLKL5J4m6PBuBuVh6ToimFXc7DWro8VHI123GCfP VhCMAYuHKFViyihkPZDXFpW5Ov69/1eI/mzmIJgPmPmtMek3oHcrg4S8jURRece1 IkhbOukwUldXZCwmm7jFuKacgn+TUqCD9cbvAMafRZRT7yL9rDhYPDm21gfMAbZY tylk5VaDX1GbV4O3ODGEFML5t9Rn8BXO8+PyrQ/HWqnIli+H98eC7GaoYtCrkZ1P MUGm/xYnooCYVqp6qCvuEUVgXg6VJZQ+0Q/sKj70bSK5SoeZCUjHLnccp8zB/Poj mZ89Uai3+XR+QVwSP41Q2vzO8ae/OdDHG3zLP/Y6DB5A+VO1xSUPMLS70HOshWcB YhD5RXw83EL7UjJccJ4O5q4JbyJU+78kPifAjaJzZEKQFk79LUKuudo5eBuLXXcp A+xdfKZtZI6AxTp3byUmUPx621Aq6aQp75VnOe73Ot+givvZSdgk7teMsdO02kHM RTvMU02CWomORK1injtOx4s2H6fZ5dz2c4lK+1SucChTwojrfFU=
=X34O
-----END PGP SIGNATURE-----
--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)