Hello Craig, it has been a week of long days as a Traffic Controller, and now getting back to this. On 2/10/19, Craig Sanders via luv-main <luv-main@luv.asn.au> wrote:
On Sun, Feb 10, 2019 at 03:50:30PM +1100, Mark Trickett wrote:
As i have mentioned, I have an Agfa SnapScan, and it appears to have died. I have bought a new scanner, and checked compatibility with the sane website. The Canon CanoScan LiDE 120 is listed as supported, but with scanimage 1.0.27, while the up to date scanimage on Debian 9.7 is 1.0.25.
the sane-utils (v 1.0.27) package in debian sid has the following dependencies:
Depends: adduser, lsb-base (>= 3.0-6), update-inetd, debconf (>= 0.5) | debconf-2.0, libavahi-client3 (>= 0.6.16), libavahi-common3 (>= 0.6.16), libc6 (>= 2.15), libieee1284-3, libjpeg62-turbo (>= 1.3.1), libpng16-16 (>= 1.6.2-1), libsane (>= 1.0.27), libsystemd0, libusb-1.0-0 (>= 2:1.0.8)
Depends: adduser, 3.115 lsb-base (>= 3.0-6), 9.20161125 update-inetd, 4.44 debconf (>= 0.5) | debconf-2.0, 1.5.61 libavahi-client3 (>= 0.6.16), 0.6.32-2 libavahi-common3 (>= 0.6.16), 0.6.32-2 libc6 (>= 2.15), 2.24-11+deb9u3 update needed libieee1284-3, 0.2.11-13 libjpeg62-turbo (>= 1.3.1), 1:1.5.1-2 libpng16-16 (>= 1.6.2-1), 1.6.28-1 libsane (>= 1.0.27), 1.0.25-4.1 update needed libsystemd0, 232-25+deb9u8 libusb-1.0-0 (>= 2:1.0.8) 2:1.0.21-1
libsane 1.0.27 doesn't have any dependencies.
So I have two packages to update, plus any dependencies of libc6 of the later version. Now to learn how to find out what that might be. And then to see where that leads. Then to install the sane-utils (v 1.0.27) package. The capacity to manage and do this is why I am using Debian, but still not sufficiently familiar with all of it. I learn by doing, but have not done enough of it to know and remember, yet.
As long as the other installed library packages are at least equal to the versions mentioned above, you should be able to just download the .deb files for sane-utils and libsane and install them with dpkg. If not, download and update them (and any of THEIR dependencies) before installing sane-utils.
i.e. download the following from your nearest debian mirror:
.../debian/pool/main/s/sane-backends/libsane_1.0.27-3.1_amd64.deb .../debian/pool/main/s/sane-backends/sane-utils_1.0.27-3.1_amd64.deb
and install them (as root) with:
dpkg -iBE libsane_1.0.27-3.1_amd64.deb sane-utils_1.0.27-3.1_amd64.deb
(or _i386.deb if you're running on an ancient CPU)
It is a 64 bit system, thanks to Russell Coker.
Alternatively, download the debianised source for sane-utils and rebuild for debian 9. i.e. make your own backport.
That has potential, but would need the backport of the libsane as well. I am not yet sure of the development and build environment, nor whether I have the necessary installed yet.
craig
PS: I note that systemd has spread its monstrous tentacles even into userland apps like sane-utils. This is why systemd is a menace - it's already nearly impossible to avoid and will soon be **actually** impossible for distros that went down the systemd path of insanity to ever disentangle themselves from RedHat's linux takeover bid.
I watched the linked video from linux.conf.au.2019, and some of the concepts behind SystemD have merit, but I do not like or agree with the implementation. While it is a number of small binaries, the package as a whole is monolithic, and I find it poorly documented. I might have troubles with the older Init, but it is documented and reasonably well known, including the deficiencies.
FFS! If systemd confined itself to just doing init and didn't assimilate or infect everything else withing reach, I wouldn't have a problem with it. But this shit really makes me hate it.
I would have less of an issue with it if they did not take an all or nothing approach, a take no prisoners approach. It reminds me of a part of Zork, "you are in a maze of twisty little passages that are all alike". For those who are not familiar with it, the learning curve is too steep.
-- craig sanders <cas@taz.net.au>
Regards, Mark Trickett