> You might not have seen my blog posts about the state of calibre in Debian, > they have been aggregated on planet.
i read it, and i considered when preparing this NMU. > Anyway, as long as I keep a Py2 version of Calibre in sid/testing, **do not** > remove Py2 support from unrardll. calibre only declares a Suggests on unrardll; as per policy https://www.debian.org/doc/debian-policy/ch-relationships.html#binary-dependencies-depends-recommends-suggests-enhances-pre-depends Suggests This is used to declare that one package may be more useful with one or more others. Using this field tells the packaging system and the user that the listed packages are related to this one and can perhaps enhance its usefulness, but that installing this one without them is perfectly reasonable. that means calibre should work perfectly fine even without unrardll. if it is more important than what Suggests means, then i guess you should consider bump it to at least Recommends. even dak, the archive toolkit, ignores Suggests when checking what would break when removing a binary package: ``` $ dak rm -Rn -b python-unrardll Will remove the following packages from unstable: python-unrardll | 0.1.3-3 | amd64 Maintainer: Norbert Preining <norb...@preining.info> ------------------- Reason ------------------- ---------------------------------------------- Checking reverse dependencies... No dependency problem found. ``` > And in addition, you might want to read up on > https://www.debian.org/doc/manuals/developers-reference/pkgs.html#nmu anything in particular you want to highlight in regards to a package in contrib, with practically no reverse depends, part of a 3300+ packages "transition"? anyhow, i cancel this NMU.. Regards, -- Sandro "morph" Tosi My website: http://sandrotosi.me/ Me at Debian: http://wiki.debian.org/SandroTosi Twitter: https://twitter.com/sandrotosi
