Hello Markus, thank you for spending your time helping to make Debian better with this bug report.
The symlinks are already created when compiling the sources. And when installing the package still copied to the right place. First I checked if there is an artifact from the upgrade stretch via Buster to Bullseye. But this is not the case and would certainly have been reported before. With the Brother packages present here some symlinks are created only with the installation, but no /usr/lib64/sane/libsane.so.1. Here however only current packages are available to me. Since the /usr/lib64/sane/libsane.so.1 does not come from the package sane-backends I close this bug. If there are new findings, please open a new bugreport. CU Jörg -- New: GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB 30EE 09F8 9F3C 8CA1 D25D GPG key (long) : 09F89F3C8CA1D25D GPG Key : 8CA1D25D CAcert Key S/N : 0E:D4:56 Old pgp Key: BE581B6E (revoked since 2014-12-31). Jörg Frings-Fürst D-54470 Lieser git: https://jff.email/cgit/ Threema: SYR8SJXB Wire: @joergfringsfuerst Skype: joergpenguin Ring: jff Telegram: @joergfringsfuerst My wish list: - Please send me a picture from the nature at your home. Am Mittwoch, dem 01.06.2022 um 01:11 +0000 schrieb Markus Kolb: > Hello again, > > I've built the version from Testing locally and with this I've found > that the problem has been a more priorised link > /usr/lib64/sane/libsane.so.1 which becomes created to a > /usr/lib64/sane/libsane-brother3.so.1.0.7. > The brother3.so is from a manually installed deb-file for my Brother > network printer. > > But I've no idea why the libsane.so.1 link is created during > installation of libsane1 package to this ...brother3.so... > > After deleting the wrong link, it uses the correct /usr/lib/x86_64- > linux-gnu/libsane.so.1 from libsane1 package and the scanimage tool > works. > Instead of deleting the link I've replaced it now with a new link > targeting the correct /usr/lib/x86_64-linux-gnu/libsane.so.1. In the > hope it stays in place for the future. > > Is it possible that the libsane-brother3.so.1.0.7 is found with a > glob like libsane*so.* and wrongly linked during libsane-common, > libsane1 or sane-utils package install?
signature.asc
Description: This is a digitally signed message part
