Comment 5 for bug 208405

So Michael and I worked together on this this week for a few hours. Unfortunately it's not a pretty story.

ISTM that part of the reason Avasys ships iscan is as a platform for the non-free binaries they provide for the scanners. Unfortunately for us, the binaries seem to go hand in hand with specific versions of iscan. For instance, for my v350 perfection scanner, I can currently only use this pair:

  iscan_2.3.0-2_i386.deb
  iscan-plugin-gt-f700_2.0.0-1_i386.deb

That's what I get when I fill the form out for my scanner model. But if you choose an all-in-one you might get 2.16.0, etc. And from my attempts, my scanner won't work with 2.16.0, and it only half works with 2.15.0 which is what Michael packaged for us.

This either needs to be resolved with Avasys, or we need to do some pretty ugly packaging where each scanner model is supported by one specific iscan package that conflicts with any other one. If any of the bug subscribers here would like to contact Avasys and let them know we're interested in figuring out how to work this through I'd be happy to chip in to the conversation.