On Sun 07 Feb 2021 at 16:15:14 +0100, Didier 'OdyX' Raboud wrote: > Control: retitle -1 sane-airscan: missing dependency on sane-utils > Control: severity -1 important > Control: tags -1 +pending > > Le samedi, 30 janvier 2021, 15.13:25 h CET Brian Potkin a écrit : > > On a system without a SANE frontend or libsane1, sane-airscan is > > effectively useless. I reckon there should be a Depends: on at > > least sane-utils. > > > > I hope the severity level is not over the top. > > Hello there Brian, and thanks for this bug report! > > traditionally, dependencies go "top-down"; from tools to libraries, and from > generic utils to backends, not in reverse. For example, libsane1 is > effectively useless on its own on my laptop; and it doesn't depend on sane- > utils. > > So, this missing dependency doesn't > * makes the package in question unusable by most or all users, or > * causes data loss, or > * introduces a security hole allowing access to the accounts of users who use > the package > (definition of the "grave" severity). > > It _does_ make it a no-op, and useless, but not "unuseable", I'd argue. Also, > the side-effect of a "grave" severity is that it makes the package subject to > auto-removal from the next stable release, as "release-critical bug". In > other > words, such a severity marks a package as unfit for release (== the release > would be better off without this package, rather than with this bug). For all > these reasons, an "important" severity seems much more adequate (to me).
No argument from me. I originally thought of "wishlist" but let myself be persuaded by what seemed like similar bug reports :). > All this said, I think it's a valid bug, and I'll therehore add a sane-utils > "Recommends"; this will pull it by default, but not enforce it. Just the ticket, I would say. Thanks for your full response. Brian.
