Le samedi, 21 septembre 2019, 10.53:04 h CEST Francesco Poli a écrit : > Should we suppose that printer-driver-hpcups reads /etc/os-release > (or /etc/issue* or /etc/debian_version) and decides whether it will > crash, based on this?!? Well. Parts of hplip are in python; and hplip then uses: import platform dist = platform.dist() platform.dist() will try to guess the Linux distro from /etc/lsb-release (should not exist), then /etc/*-{release,version}, hence /etc/os-release. hplip uses its own internal list of supported distros, in /usr/share/hplip/installer/distros.dat … shipped from hplip-data. It only gained "Buster" support in 3.19.8; so could any of you try to install distros.dat from https://salsa.debian.org/printing-team/hplip/raw/debian/3.19.8+dfsg0-3/ installer/distros.dat into /usr/share/hplip/installer/distros.dat, and try printing again? (That is: wget -q 'https://salsa.debian.org/printing-team/hplip/raw/debian/ 3.19.8+dfsg0-3/installer/distros.dat' -O - | sudo tee /usr/share/hplip/ installer/distros.dat ) I'm not sure it will work, as printer-driver-hpcups doesn't depend on hplip- data anyway; *sigh*. (It seems this whole "detect the distro and try being smart" should be removed completely from Debian's hplip). Cheers, OdyX
Attachment:
signature.asc
Description: This is a digitally signed message part.