The site I ended on initially was this one: http://support.epson.net/linux/en/imagescanv3.php?version=1.3.21
It offers specific drivers for leading distros. I chose Fedora because I thought that package would be most compatible with Mageia. The package is labeled as an "RPM" package, but once you extract the tar archive components you discover it is actually a binary that contains and obscures the RPMs. When I ran binaries for both Fedora 25 and Fedora 26, each failed a different dependency and thus neither would install.
I then found actual Fedora 26 RPM packages on http://www.pkgs.org which is a Ukrainian site that distributes packages from the Russian Fedora distribution. Those worked flawlessly.
Then I discovered yet another Epson download site: http://support.epson.net/linux/en/iscan_c.php?version=1.0.4
This appears to be a much older version, but it actually contains the real RPM packages which were actually versioned newer than the Fedora 26 I got from pkgs.org.
With these packages the iscan package installed flawlessly but the iscan-data package failed on the clean up scripts.
- Code: Select all
[root@localhost data]# rpm -Uvh iscan-data-1.39.0-1.noarch.rpm
Preparing... ################################# [100%]
Updating / installing...
1:iscan-data-1.39.0-1 ################################# [ 50%]
Cleaning up / removing...
2:iscan-data-1.36.0-15.2 ################################# [100%]
^Cwarning: %triggerin(glibc-6:2.22-25.mga6.x86_64) scriptlet failed, signal 2
But the script failure did not affect Xsane functionality. Everything still worked OK.
I am hoping that this information might prove useful to anyone encountering this confusing situation with Epson drivers.