Please bump sane-backends to 1.0.22, it includes among other things a new magicolor backend to support the Konica Minolta 1690MF.
I am aware of the release, but it could take some time since I'm not at home... Thanks for the hint, anyway.
Created attachment 264117 [details] Draft ebuild for sane-backends-1.0.22 release I created ebuild for 1.0.22 release from 1.0.21-r1. It's my first ebuild, but it works.
Patrick, I could do a quick bump for you if you wish - just hit a need for it myself, previous version oes not support latest cheapest canon scanner (LIDE 110). Basic rename does most of the work, to make it build I needed to only remove two lines in src_unpack: the ebuild would need to lose i18n (no translations upstream as of yet) and xerox-grey.patch - fails on all files. Just let me know..
I would also be willing to test 1.0.22. I just bought a CanoScan LiDE 210 which is reported to work very well, but only in 1.0.22.
Patrick, please give us a ack, I'm also in need for .22 release so ...
Created attachment 270947 [details] ebuild patch This is a patch over the 21-r1 ebuild: - it adds to the list the two new backends introduced with .22; - it ports it to EAPI=4 just to be on the latest version (you never know which features you might need in the future, the virtual/mta debacle is making me feel like we should kill old EAPIs altogether); - avoids a couple of directory changes just for the sake of removing code; - adds epkowa to the list of backends like it's done for hplip (for Avasys's drivers for Epson scanners); - uses emake for install and dies if install fails. This should be all of it.
1.21-r1 doesn't help my situation, as the drivers for my Canon LiDE 210 are only available in 1.22. Andrey, I got the ebuild file from your upload, but it doesn't work without a Manifest. Patrick, I'm quite a novice when it comes to working with ebuilds, but if there is anything I can do to help get the port for 1.22 ready, I would be happy to help.
I was able to download and successfully build 1.0.22 manually as long as I ran the configure script with the "--enable-libusb_1_0" option. It will find the scanner and root can run xsane, but there is some gentoo integration that Patrick's ebuild did that I'm not getting right because I cannot run "scanimage -L" as a user and get results. Recommended permissions changes haven't helped. I guess my point is that it may not be hard to get it to build correctly once Patrick (or someone) has the time to do all the same "magic" to the 1.0.22 ebuild file as was done to the 1.0.21.
Created attachment 272479 [details] unofficial sane-backends-1.0.22 ebuild
Using the 1.0.21-r1 ebuild file, I created one for 1.0.22. This is my first attempt at creating an ebuild, so it's probably not very robust. However, it does take the use flag libusb_1 to use libusb-1.0, which is required by my genesys driver. It downloaded, built, and installed fine and I'm using it with my CanoScan. I have uploaded the ebuild if anyone is interested.
Michael, please replace your ebuild with an ebuild patch (diff -u old.ebuild new.ebuild). As for libusb-1, I haven't looked into that yet, but why do you say it is needed by your driver? If sane-backends can work with libusb-1, we should probably just move it to use that and not libusb-0. For now though, I guess that unless Patrick says otherwise I'll commit at least my version next week, so if you can give me the ebuild diff I'll look into integrating what you changed as well.
Created attachment 272503 [details, diff] ebuild patch from 1.0.21-r1 to 1.0.22
Diego, I don't know how to make the "unofficial" obsolete, but I have uploaded the diff between 1.0.21-r1 and 1.0.22. I need the genesys driver from 1.0.22 to support my CanoScan LiDE 210. I don't remember where I read it, but I found docs that said that the genesys driver needs libusb >= 1.0.18 or something like that. I hope the changes I made are useful. As I said, I've not created ebuilds before, so this probably has some problems for the general case. But for mine, it built, installed, and set permissions so that I could use it as a regular user just as I had hoped.
Michael I committed my current 1.0.22 that still uses libusb-0.1 — using libusb-1.0 could create a couple of issues to epkowa and I'd like to test that first. Please open a bug and CC me directly if your scanner fails with the genesys backend with my ebuild, if so I'll see to take care of it. Thanks!
Diego, as you probably noticed, I added a USE flag for libusb v1.x, but I also removed the effect of the USE flag usb (which enabled libusb v0.y). I will try your ebuild using libusb_0 and see if genesys still works for me. Thanks!
Diege, I built your 1.0.22 port and it works fine. I verified that it's using libusb-0: sane-backends # ldd /usr/bin/scanimage linux-vdso.so.1 => (0x00007fff39fef000) libsane.so.1 => /usr/lib/libsane.so.1 (0x00007f3e07c12000) libc.so.6 => /lib/libc.so.6 (0x00007f3e078b8000) libpthread.so.0 => /lib/libpthread.so.0 (0x00007f3e0769c000) libv4l1.so.0 => /usr/lib/libv4l1.so.0 (0x00007f3e07496000) libtiff.so.3 => /usr/lib/libtiff.so.3 (0x00007f3e07233000) libz.so.1 => /lib/libz.so.1 (0x00007f3e0701c000) libm.so.6 => /lib/libm.so.6 (0x00007f3e06d9b000) libjpeg.so.8 => /usr/lib/libjpeg.so.8 (0x00007f3e06b61000) libusb-0.1.so.4 => /lib/libusb-0.1.so.4 (0x00007f3e06958000) libavahi-client.so.3 => /usr/lib/libavahi-client.so.3 (0x00007f3e06747000) libdbus-1.so.3 => /usr/lib/libdbus-1.so.3 (0x00007f3e06504000) librt.so.1 => /lib/librt.so.1 (0x00007f3e062fb000) libavahi-common.so.3 => /usr/lib/libavahi-common.so.3 (0x00007f3e060ee000) libdl.so.2 => /lib/libdl.so.2 (0x00007f3e05eea000) /lib64/ld-linux-x86-64.so.2 (0x00007f3e07e35000) libv4l2.so.0 => /usr/lib/libv4l2.so.0 (0x00007f3e05cdf000) libv4lconvert.so.0 => /usr/lib/libv4lconvert.so.0 (0x00007f3e05a6e000) sane-backends # and that I can use xsane to scan an image. I must have misread something that I thought I needed libusb.1.x. Thank you again for your work. Is there anything else I can do to help you with this ebuild?
Well, since .22-r1 has been in CVS for quite a while, I think this can be considered finished. Thank you all very much!
