On Sun, 11 Nov 2018 09:07:05 +0100 Gianfranco Costamagna <locutusofb...@debian.org> wrote: > Control: -1 severity serious > > > > > > Hi, > > > > libsane1 has been renamed to libsane. > > > > apt install libsane > > > > will remove libsane1 and install libsane which should resolve your issue. > > > > I beg to disagree, some external packages (mostly deb files from external > vendors), are requiring explictly > libsane1 dependency (this is the reason for it being provided in first > place), and repacking them to use > libsane is not feasible inside Debian context,
Well, it's actually the other way around. All 3rd party packages I know depend on libsane, not the new libsane1 name. so maybe the severity "serious" is appropriate even > if inside the Debian archive there is no such issue. That said, the new-old libsane *does* provide libsane1, so packages which actually do depend on libsane1 will not be broken. It's just that apt (or aptitude) will not automatically replace the old libsane1 with the new-old libsane on upgrades. One can help apt a bit to do the right thing e.g. via # apt full-upgrade libsane Not sure what the right severity is for this issue and if it's worth fixing, giving that the real libsane1 package was only ever in unstable and never made it to testing or a stable release. Regards, Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
