date:20090127

Julien BLACHE jb at jblache.org writes:

 Olaf Meeuwissen olaf.meeuwissen at avasys.jp wrote:

 Hi,

 Changes to epkowa.desc (against the CVS snapshot of 2009-01-22) are
 attached.  If some kind soul with commit privileges could add these
 I'd be grateful, yet again.

 Done.

Many thanks!
-- 
Olaf Meeuwissen, LPIC-2   FLOSS Engineer -- AVASYS Corporation
FSF Associate Member #1962   Help support software freedom
 http://www.fsf.org/jf?referrer=1962

[sane-devel] iscan and apt dependencies

Paul Fox pgf at foxharp.boston.ma.us writes:

 hi --

 i've installed the latest iscan debs to support my epson v500:
 iscan-plugin-gt-x770_2.1.0-1_i386.deb
 iscan_2.15.0-3_i386.deb

 iscan won't install normally because it depends on libltdl3,
 which isn't available on ubuntu 8.10 (which has libltdl7 installed).

 i also can't just install the plugin .deb, because it depends on
 the iscan .deb, which needs libltdl3.

 however, after forcing the install with:
 dpkg -i --ignore-depends=libltdl3 iscan_2.15.0-3_i386.deb
 and symlinking libltdl.so.7 to libltdl.so.3, iscan and all of the
 sane front-ends work fine.

 so at the least, this message is a bug report against the current
 iscan dependencies.  (btw, i'm not sure i understand how this should be
 resolved.)

Eh, no.  This is a limitation on our binary packages.  Please have a
look at the KNOWN-PROBLEMS and rebuild from source.  The source's
build dependencies support building with either version of libltdl-dev
installed.

Ubuntu kindly decided there was no need for a phase out of libltdl3
and dropped it completely in favour of libltdl7.  There is at least
one package in the Ubuntu universe (multiverse?) that suffers from
the same problem.

 but now i'm not sure whether i forced the installation correctly,
 because i'm now kind of stuck (and maybe this is an apt
 question).  i can't install or upgrade anything else because apt
 thinks iscan is broken, and keeps insisting on trying to remove
 it when it performs any other action.

 any ideas on how to work around this?

See above.  Alternatively, you could have a look at using equivs and
create a meta-package that provides libltdl3.  There may be useful
info in the Ubuntu Forum post mentioned in the KNOWN-PROBLEMS file as
well.

Hope this helps,
-- 
Olaf Meeuwissen, LPIC-2   FLOSS Engineer -- AVASYS Corporation
FSF Associate Member #1962   Help support software freedom
 http://www.fsf.org/jf?referrer=1962

[sane-devel] Providing the version of SANE used in VueScan

Ed Hamrick EdHamrick at aol.com writes:

 My name is spelled Hamrick - with one m.
 It's polite to sign e-mails with one's name.

Hi Ed,

 The source code to sanei_scsi.c is attached.

You missed sanei_config.c and sanei_debug.c and the various header
files below include/sane/ that these three include.

 Of course, you're just wasting your time and
 my time, which is annoying at best.  These
 childish games aren't amusing for me or
 for anyone reading this mailing list.

If you think these kind of legitimate requests waste your time, you
are of course free to drop the source code that you reused from the
SANE project and write your own so no-one can bother you with these
annoyances.

 sanei_config
 SANE_CONFIG_DIR
 .:/usr/local/etc/sane.d
 sanei_config_open: attempting to open `%s'
 sanei_config_open: using file `%s'
 sanei_config_open: could not find config file `%s'
 sanei_debug
 SANE_DEBUG_
 [sanei_debug] malloc() failed

Hope this helps,
-- 
Olaf Meeuwissen, LPIC-2   FLOSS Engineer -- AVASYS Corporation
FSF Associate Member #1962   Help support software freedom
 http://www.fsf.org/jf?referrer=1962

[sane-devel] Epson V200 Scanner, 64Bit Ubuntu

2009-01-27 Thread Patrick Scheibe

Hi,

I want to use an Epson V200 Photo USB Scanner on my Linux Box:

Ubuntu 8.04
64 Bit
2.6.24-23-generic Kernel

When I understood this right then I need 2 things: the epkowa-backend
and a proprietary plug-in which is only available as binary under
http://avasys.jp/hp/menu00500/hpg00442.htm.
The backend is included in the libsane-extras package and the epkowa.c
file seems similar to the one included in my distribution. Per accident
I stumbled over the README in the doc directory saying:


The following scanners require the use of a proprietary module to work
with the epkowa backend...
snip
You can download the module and firmware files from the Epson Avasys
website at:
 http://www.avasys.jp/english/linux_e/index.html
 The module and firmware files are distributed in the form of an RPM
package;
 you'll need to install the rpm and cpio Debian packages to extract the
content
 of the RPM file:
  - rpm2cpio iscan-plugin-rpm  foo.cpio
  - cpio -i --make-directories --no-absolute-filenames  foo.cpio
 The module and firmware files will be available in the usr/lib/iscan
and
 usr/share/iscan directories, relative to the current directory. You
need
 to copy the module files to /usr/lib/iscan and the firmware file to
 /usr/share/iscan.


This is what I did but the scanner isn't found with scanimage -L. I
checked after running ldconfig whether the libs are included in the
lib-cache but I couldn't find it.
I'm afraid that the proprietary libraries need to be 64bit libs.

Does anyone has a clue for me.

Cheers
Patrick

[sane-devel] Epson V200 Scanner, 64Bit Ubuntu

2009-01-27 Thread Ivan Boldyrev

On Tue, Jan 27, 2009 at 10:09 AM, Patrick Scheibe patrick at yoursort.de 
wrote:
 Hi,

 I want to use an Epson V200 Photo USB Scanner on my Linux Box ...
 I'm afraid that the proprietary libraries need to be 64bit libs.

I have same problem; Avasys recently promised to release 64-bit
version of the plugin, but I slowly working on open-source driver.

The possible solutions:

1. Wait before someone (be it me or some else) release open-source driver.
2. Wait before Avasys release 64-bit version of plugin.
3. Run 32 bit chroot and talk with 32-bit part over TCP/IP.
4. Switch to 32 bits.

P.S. 4ALL:  I was wrong, and V200 has binary mode; and it seems I can
soon release driver for binary mode; I haven't experimented with
grayscale much.  I'm sorry I haven't release my current results yet,
but I had little time...  I will try really hard :)

-- 
Ivan Boldyrev

[sane-devel] Usage of LIBOBJS/ALLOCA in Makefiles

Chris Bagwell chris at cnpbagwell.com writes:

 [snip]
 Second question is this:  I don't think its a good idea to link internal 
 versions of standard functions into the backends.  As I mentioned 
 earlier, its super common for all projects to do this.  If we link in, 
 for example, snprintf into libsane and then if someone else links in 
 libsane along with their own internal snprintf then we will get symbol 
 collisions and failed compiles.

ACK.

 In the past, I've worked around this issue by using preprocessor magic.  
 When we detect internal version will be used then add a #define 
 snprintf sanei_snprintf to some global header file.  Then normal code 
 keeps referring to just snprintf() but it sometimes get remapped to 
 internal version without library knowing it.  Exported symbol table will 
 be proper sanei_ prefix as well.

SANE backends should not export sanei_ symbols.  The preprocessor
magic you suggest sounds fine to me.

Hope this helps,
-- 
Olaf Meeuwissen, LPIC-2   FLOSS Engineer -- AVASYS Corporation
FSF Associate Member #1962   Help support software freedom
 http://www.fsf.org/jf?referrer=1962

[sane-devel] Avision bug (was: Re: Suicidal Child Process - SANE)

2009-01-27 Thread Mattias Ellert

This one bounced, trying to resend.

Mattias

Vidarebefordrat meddelande
Fr?n: Mattias Ellert mattias.ellert at fysast.uu.se
Till: m.allann oah kitno455 at gmail.com
Kopia: SANE sane-devel at lists.alioth.debian.org
?mne: Re: [sane-devel] Avision bug (was: Re: Suicidal Child Process -
SANE)
Datum: Sun, 25 Jan 2009 17:11:50 +0100

15 jan 2009 kl. 03.09 skrev m. allan noah:

On Sun, Jan 11, 2009 at 8:46 AM, m. allan noah kitno455 at gmail.com
wrote:
On Sun, Jan 11, 2009 at 8:10 AM, Mattias Ellert
mattias.ellert at fysast.uu.se wrote:
22 dec 2008 kl. 02.31 skrev m. allan noah:

On Tue, Dec 9, 2008 at 10:48 AM, Mattias Ellert
mattias.ellert at fysast.uu.se wrote:

m?n 2008-12-08 klockan 09:46 -0500 skrev m. allan noah:

After some private mails with Ian, it seems this is a bug in
sane-avision:

during sane_cancel(), the backend calls: sanei_thread_kill
(s-reader_pid), but s-reader_pid is 0, which signals the
entire
group. There is a test to try and avoid this, but it relies on
prior
code to have set s-reader_pid = -1, which has not happened in
the
case of no paper.

I just expanded the test to require a positive value, since
the pid
should never be negative anyway? My fix has just been commited
to CVS
(backend version 289 nice round number for Ford and Studebaker
fans).
Ian and Rene- please test.

allan

This breaks the MacOS X port. The PID number (being a pointer)
can be
arbitrary large, and when cast to an integer it can easily
overflow to a
negative value. The code was fixed for this problem by removing
all
places where the code was checking for a PID 0. For the avision
backend this was done here:

https://alioth.debian.org/plugins/scmcvs/cvsweb.php/sane-backends/backend/avision.c.diff?r1=1.38;r2=1.39;cvsroot=sane

Your commit:

https://alioth.debian.org/plugins/scmcvs/cvsweb.php/sane-backends/backend/avision.c.diff?r1=1.43;r2=1.44;cvsroot=sane

reintroduces the problem fixed by the earlier commit. Please
revert it
and fix the new problem in a way that doesn't break the MacOS X
port.

Ok, so what is the correct fix? If OSX is using pthread, is it
enough
to make SANE_Pid pthread_t?

allan

The SANE_Pid is properly declared as:

#ifdef USE_PTHREAD
typedef long SANE_Pid;
#else
typedef int SANE_Pid;
#endif

This gives the correct size for both fork and pthread on both 32
and 64 bit.
Changing it to pid_t and pthread_t instead of int and long would
mean an
interface change (and we get into the change soname or not
discussion again)
- you would also loose the abstraction achieved by using an opaque
type in
the SANE API rather than the implementation specific types.

Correct me if i am wrong, but we are talking about sanei here, not
the
sane API. None of this is in the API.

Yes, it is not in the SANE client API. It is in sanei, which is part
of the API for writing SANE backends. Sorry for being unclear, but you
seem to have got what I meant anyway.

Also since the SANE API states that a SANE_Pid value of -1
indicates an
error, the SANE_Pid must be a signed type.

Where does it state this? I dont see SANE_Pid anywere in the API.

Changing it to pthread_t (which
essentially is a pointer - hence an unsigned type) will break the
API badly.
Any value for a unsigned type will always be different from -1 (a
good
compiler will optimise the check away).

The only thing that must remembered is that negative values for
SANE_Pid are
valid (except for -1). You can not check for a valid SANE_Pid with
(pid
0).

Pointers could wrap to -1 as well. This fix is not sufficient. I
think
we can correct this the right way in sanei.

Ok, I've done a little bit of digging, and it appears that we can fix
this by making SANE_Pid an int which we use as an index into an array
of platform-specific types, like pthread_t or such. Then we can
specifically disallow certain values like anything 1.

comments?

I am not sure what you are trying to achieve. I am perfectly happy
with the current implementation of sanei-thread. I just pointed out
that your latest change to your backend code violates this current
implementation. If you insist on your changes to your backend code the
sanei-thread implementation must be changed to allow your backend to
run, but doesn't it make more sense to make your backend compatible to
the current sanei-thread implementation rather than doing it the other
way around?

Mattias

-- next part --
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 2272 bytes
Desc: not available
Url :
http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20090127/8adaf4e9/attachment-0001.bin

[sane-devel] Avision bug (was: Re: Suicidal Child Process - SANE)

2009-01-27 Thread Mattias Ellert

This one bounced, trying to resend.

Mattias

 Vidarebefordrat meddelande 
Fr?n: Mattias Ellert mattias.ellert at fysast.uu.se
Till: SANE sane-devel at lists.alioth.debian.org
?mne: Re: [sane-devel] Avision bug (was: Re: Suicidal Child Process -
SANE)
Datum: Mon, 26 Jan 2009 22:00:11 +0100

25 jan 2009 kl. 18.08 skrev m. allan noah:


 ok, I'll say it a third time, but phrase it as a question: Could this
 pointer also wrap to -1 as well?

 allan



Due to memory alignment the pthread pointer is always an even address,  
hence can not overflow to -1.

Mattias

-- next part --
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 2272 bytes
Desc: not available
Url : 
http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20090127/9a6c2dc3/attachment.bin

[sane-devel] build sane-backends on Mac OS X -- 10.5.*

Chris Bagwell chris at cnpbagwell.com wrote:

Hi,

 OK, I'll submit this soon as I have a chance to test it... I've not
 used it before but I assume it makes things no worse then they are
 today (I mean that today you have to rerun ./configure or similar any
 time you modify Makefile.in to make those changes go into affect and
 same will apply to Makefile.am's).

Yes, it will just require you (or anyone working on autofoo) to pass
--enable-maintainer-mode at configure time, while everybody else won't
have to endure the autotools run due to (harmless, here) timestamp
skew :)

JB.

-- 
Julien BLACHE   http://www.jblache.org 
jb at jblache.org  GPG KeyID 0xF5D65169

[sane-devel] Providing the version of SANE used in VueScan

Ed Hamrick EdHamrick at aol.com wrote:

 VueScan.  And yes, I'm obviously capable of spending
 an hour or two stripping the sanei_scsi module

An hour or two? To replace sanei_scsi? Funny one.

JB.

-- 
Julien BLACHE   http://www.jblache.org 
jb at jblache.org  GPG KeyID 0xF5D65169

[sane-devel] Providing the version of SANE used in VueScan

2009-01-27 Thread abel deuring

On 27.01.2009 07:30, Ed Hamrick wrote:
 Hi Olaf,
 
 The source you referred to is attached.  I'm happy
 to assist people with getting copies of the source
 code to the trivial parts of SANE that I used in
 VueScan.  And yes, I'm obviously capable of spending
 an hour or two stripping the sanei_scsi module
 out of VueScan - after all, VueScan does support many
 things (like infrared cleaning) on Epson scanners that
 you're incapable of supporting :)

Actually, I'd appreciate if you would remove sanei_scsi from Vuescan. I
remember a bug report from a Vuescan user a few years ago who stumbled
over a sanei_scsi bug. I could fix this bug quickly -- but the poor user
was out of luck: you wrote that you hadn't had enough time to link the
fixed sanei_scsi version into a new Vuescan release...

That was a reason why I always considered to start a discussion if Sane
shouldn't switch to the LGPL: It would allow Vuescan users to link a
fixed Sane library into Vuscan and other proprietary programs for
themselves.

 
 This is also an official request to Ren? Rebe to
 provide the source code to avision.c that he's included
 in ExactScan 2.

Yeah -- the funny thing with this request is that it was Rene who wrote
the avision backend. So your request may be formally valid, but,
frankly, it looks a bit weird.

Abel

[sane-devel] Epson V200 Scanner, 64Bit Ubuntu

2009-01-27 Thread Patrick Scheibe

Hi Ivan,

thank you for this information. I'll try to install it on my 32bit
machine.

Cheers
Patrick

On Tue, 2009-01-27 at 11:33 +0600, Ivan Boldyrev wrote:
 On Tue, Jan 27, 2009 at 10:09 AM, Patrick Scheibe patrick at yoursort.de 
 wrote:
  Hi,
 
  I want to use an Epson V200 Photo USB Scanner on my Linux Box ...
  I'm afraid that the proprietary libraries need to be 64bit libs.
 
 I have same problem; Avasys recently promised to release 64-bit
 version of the plugin, but I slowly working on open-source driver.
 
 The possible solutions:
 
 1. Wait before someone (be it me or some else) release open-source driver.
 2. Wait before Avasys release 64-bit version of plugin.
 3. Run 32 bit chroot and talk with 32-bit part over TCP/IP.
 4. Switch to 32 bits.
 
 P.S. 4ALL:  I was wrong, and V200 has binary mode; and it seems I can
 soon release driver for binary mode; I haven't experimented with
 grayscale much.  I'm sorry I haven't release my current results yet,
 but I had little time...  I will try really hard :)
 
 -- 
 Ivan Boldyrev

[sane-devel] Stef: HP G2410 Test

2009-01-27 Thread Robert John Morton

Hello Stef

I have been on a summer holiday so I could not do the test earlier.
I downloaded the new version of sane-backends-genesys from your web page.
I configured it with |./configure --enable-libusb and then ran make|
I then attached and switched on the scanner,
changed to the backend directory and ran ./run-genesys
Absolutely nothing happened.
I commented out the 600dpi line in run-genesys and re-ran it.
Again, nothing happened.
This is a completely new installation of sane-backends-genesys so do I 
need to uncomment an hp2400c line anywhere?

Regards, Rob


stef wrote:
   Hello,

   the genesys backend as been updated. Thanks to an hardware donation of 
 Jack 
 McGill, there is now support for the sheet-fed Visioneer Strobe XP200. It can 
 scan at 75, 100, 200, 300 and 600 dpi in color or gray and at 8 or 16 bits. 
 Scans are uncalibrated, ie there is no shading nor gain calibration. The next 
 step is to add calibration which use an external sheet with printed patterns. 
   There is also button support for the Medion 534, the HP 2300 and Strobe 
 XP200
   The 'motor bug' at 100 dpi for gray scans affecting the MD5345 is still 
 unresolved.
   The backend should also now be able to scan at 50 or 300 dpi with an 
 HP2400.

 Regards,
   Stef

[sane-devel] Stef: HP G2410 Tests

2009-01-27 Thread Robert John Morton

Hello Stef

Xsane registers the presence of genesys as a valid scanner
As far as I can determine, the HP driver for the 2400/g2410,
used via Xsane, supports 150, 200, 300, 60, 1200 dpi.
It does not support 50, 75, 100.
Perhaps there is a mechanical reason for this.

Re my previous post, I thought I might have a permissions problem so I 
gave all users permission to access /dev/bus/usb/003/005, which is used 
for my G2410.

Still nothing happened when I execute ./run-genesys in /backend

Hope this helps. Regars, Rob

[sane-devel] Providing the version of SANE used in VueScan

On Tue, Jan 27, 2009 at 8:01 AM, abel deuring adeuring at gmx.net wrote:
 On 27.01.2009 07:30, Ed Hamrick wrote:
 Hi Olaf,

 The source you referred to is attached.  I'm happy
 to assist people with getting copies of the source
 code to the trivial parts of SANE that I used in
 VueScan.  And yes, I'm obviously capable of spending
 an hour or two stripping the sanei_scsi module
 out of VueScan - after all, VueScan does support many
 things (like infrared cleaning) on Epson scanners that
 you're incapable of supporting :)

 Actually, I'd appreciate if you would remove sanei_scsi from Vuescan. I
 remember a bug report from a Vuescan user a few years ago who stumbled
 over a sanei_scsi bug. I could fix this bug quickly -- but the poor user
 was out of luck: you wrote that you hadn't had enough time to link the
 fixed sanei_scsi version into a new Vuescan release...

 That was a reason why I always considered to start a discussion if Sane
 shouldn't switch to the LGPL: It would allow Vuescan users to link a
 fixed Sane library into Vuscan and other proprietary programs for
 themselves.


 This is also an official request to Ren? Rebe to
 provide the source code to avision.c that he's included
 in ExactScan 2.

 Yeah -- the funny thing with this request is that it was Rene who wrote
 the avision backend. So your request may be formally valid, but,
 frankly, it looks a bit weird.

No, it is not weird at all. The GPL is not to punish Rene, it is to
give rights to Ed (and everyone else). If he has received a legitimate
copy of ExactScan, he is entitled to the SANE portions. Since
ExactScan comes as a free trial, everyone is a legitimate user. There
seems to be no other way to get this code than asking Rene directly.

allan

ps- these license issues would be clarified by switching to the LGPL,
but because the copyright holder of SANE is each individual author,
you would have to get all of their permission. An impossible task,
IMHO.
-- 
The truth is an offense, but not a sin

[sane-devel] Providing the version of SANE used in VueScan

m. allan noah kitno455 at gmail.com wrote:

 No, it is not weird at all. The GPL is not to punish Rene, it is to
 give rights to Ed (and everyone else). If he has received a legitimate
 copy of ExactScan, he is entitled to the SANE portions. Since
 ExactScan comes as a free trial, everyone is a legitimate user. There
 seems to be no other way to get this code than asking Rene directly.

Except if Rene is the sole copyright holder* on the avision backend, in
which case he can do whatever pleases him with the code. Don't forget
this, hrm, detail.

(*) or other copyright holders agreed to that

JB.

-- 
Julien BLACHE   http://www.jblache.org 
jb at jblache.org  GPG KeyID 0xF5D65169

[sane-devel] Providing the version of SANE used in VueScan

2009-01-27 Thread abel deuring

On 27.01.2009 18:28, m. allan noah wrote:
 On Tue, Jan 27, 2009 at 8:01 AM, abel deuring adeuring at gmx.net wrote:
 On 27.01.2009 07:30, Ed Hamrick wrote:
 Hi Olaf,

 The source you referred to is attached.  I'm happy
 to assist people with getting copies of the source
 code to the trivial parts of SANE that I used in
 VueScan.  And yes, I'm obviously capable of spending
 an hour or two stripping the sanei_scsi module
 out of VueScan - after all, VueScan does support many
 things (like infrared cleaning) on Epson scanners that
 you're incapable of supporting :)
 Actually, I'd appreciate if you would remove sanei_scsi from Vuescan. I
 remember a bug report from a Vuescan user a few years ago who stumbled
 over a sanei_scsi bug. I could fix this bug quickly -- but the poor user
 was out of luck: you wrote that you hadn't had enough time to link the
 fixed sanei_scsi version into a new Vuescan release...

 That was a reason why I always considered to start a discussion if Sane
 shouldn't switch to the LGPL: It would allow Vuescan users to link a
 fixed Sane library into Vuscan and other proprietary programs for
 themselves.

 This is also an official request to Ren? Rebe to
 provide the source code to avision.c that he's included
 in ExactScan 2.
 Yeah -- the funny thing with this request is that it was Rene who wrote
 the avision backend. So your request may be formally valid, but,
 frankly, it looks a bit weird.
 
 No, it is not weird at all. The GPL is not to punish Rene, it is to
 give rights to Ed (and everyone else). If he has received a legitimate
 copy of ExactScan, he is entitled to the SANE portions. Since
 ExactScan comes as a free trial, everyone is a legitimate user. There
 seems to be no other way to get this code than asking Rene directly.

As Julien aleady wrote, if Rene is the only author of the backend he can
whatever he wants with the code.

 
 allan
 
 ps- these license issues would be clarified by switching to the LGPL,
 but because the copyright holder of SANE is each individual author,
 you would have to get all of their permission. An impossible task,
 IMHO.

Agreed. That's the main reason why I did not start this discussion.

Abel

[sane-devel] Providing the version of SANE used in VueScan

On Tue, Jan 27, 2009 at 2:00 PM, abel deuring adeuring at gmx.net wrote:
 On 27.01.2009 18:28, m. allan noah wrote:
 On Tue, Jan 27, 2009 at 8:01 AM, abel deuring adeuring at gmx.net wrote:
 On 27.01.2009 07:30, Ed Hamrick wrote:
 Hi Olaf,

 The source you referred to is attached.  I'm happy
 to assist people with getting copies of the source
 code to the trivial parts of SANE that I used in
 VueScan.  And yes, I'm obviously capable of spending
 an hour or two stripping the sanei_scsi module
 out of VueScan - after all, VueScan does support many
 things (like infrared cleaning) on Epson scanners that
 you're incapable of supporting :)
 Actually, I'd appreciate if you would remove sanei_scsi from Vuescan. I
 remember a bug report from a Vuescan user a few years ago who stumbled
 over a sanei_scsi bug. I could fix this bug quickly -- but the poor user
 was out of luck: you wrote that you hadn't had enough time to link the
 fixed sanei_scsi version into a new Vuescan release...

 That was a reason why I always considered to start a discussion if Sane
 shouldn't switch to the LGPL: It would allow Vuescan users to link a
 fixed Sane library into Vuscan and other proprietary programs for
 themselves.

 This is also an official request to Ren? Rebe to
 provide the source code to avision.c that he's included
 in ExactScan 2.
 Yeah -- the funny thing with this request is that it was Rene who wrote
 the avision backend. So your request may be formally valid, but,
 frankly, it looks a bit weird.

 No, it is not weird at all. The GPL is not to punish Rene, it is to
 give rights to Ed (and everyone else). If he has received a legitimate
 copy of ExactScan, he is entitled to the SANE portions. Since
 ExactScan comes as a free trial, everyone is a legitimate user. There
 seems to be no other way to get this code than asking Rene directly.

 As Julien aleady wrote, if Rene is the only author of the backend he can
 whatever he wants with the code.

true enough. Though with patches from users/authors, this is an ideal
state rarely reached.



 allan

 ps- these license issues would be clarified by switching to the LGPL,
 but because the copyright holder of SANE is each individual author,
 you would have to get all of their permission. An impossible task,
 IMHO.

 Agreed. That's the main reason why I did not start this discussion.

Yes, it seems that some projects are assigning copyright to a single
entity just to avoid this problem.

allan
-- 
The truth is an offense, but not a sin

[sane-devel] Avision.c copyrights

2009-01-27 Thread Ed Hamrick

Ren? Rebe isn't the sole copyright holder of avision.c,
and he's been making modifications that he hasn't
been putting into SANE.  The other copyright holders are:

Meino Christian Cramer
Jose Paulo Moitinho de Almeida

Other contributors (who contributed based on the GPL provisions):

Gunter Wagner
Martin Jel?nek
Marcin Siennicki
Frank Zago
Avision INC
Franz Bakan
Falk Rohsiepe

I've asked him to release the source code to avision.c, and
I'm waiting to see it.  I want to see how he got the Xerox
DocuMate 150 working in avision.c.  I don't have one, and
one of my customers wants to use it with VueScan.

Regards,
Ed Hamrick

[sane-devel] Providing the version of SANE used in VueScan

m. allan noah kitno455 at gmail.com wrote:

 Yes, it seems that some projects are assigning copyright to a single
 entity just to avoid this problem.

Which is not legal/possible in some countries to begin with, so it's
really moot for anything contributed by people from these countries.

JB.

-- 
Julien BLACHE   http://www.jblache.org 
jb at jblache.org  GPG KeyID 0xF5D65169

[sane-devel] Another ADD-ON for descfiles :scsi-entry for GT 7000 from EPSON

2009-01-27 Thread Dieter Jurzitza

Dear listmembers,
I found one more scanner in the meantime that needs to be integrated to the 
descfile-patches. Tested and found to be functional since today.

Again, full patch against 1.0.19 attached (an EPSON-device this time)
Thank you very much,
take care



Dieter Jurzitza

@Julien Blanche: would you kindly apply?

-- 
---

   |
\
 /\_/\   |
| ~x~ |/-\   /
 \   /-   \_/
  ^^__   _/  _     /
 ??__ \- \_/ |  |/|  |
  ||  || _| _|_| _|

if you really want to see the pictures above - use some font
with constant spacing like courier! :-)
---
-- next part --
A non-text attachment was scrubbed...
Name: sane-backends-1.0.19-descfiles.patch
Type: text/x-diff
Size: 1185 bytes
Desc: not available
Url : 
http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20090127/69ff4945/attachment.patch

[sane-devel] Avision.c copyrights

On Tue, Jan 27, 2009 at 1:56 PM, Ed Hamrick EdHamrick at aol.com wrote:
 Ren? Rebe isn't the sole copyright holder of avision.c,
 and he's been making modifications that he hasn't
 been putting into SANE.  The other copyright holders are:

 Meino Christian Cramer
 Jose Paulo Moitinho de Almeida

 Other contributors (who contributed based on the GPL provisions):

 Gunter Wagner
 Martin Jel?nek
 Marcin Siennicki
 Frank Zago
 Avision INC
 Franz Bakan
 Falk Rohsiepe

 I've asked him to release the source code to avision.c, and
 I'm waiting to see it.  I want to see how he got the Xerox
 DocuMate 150 working in avision.c.  I don't have one, and
 one of my customers wants to use it with VueScan.


A reasonable request, however it makes your Avision support code a
derivative of of SANE, and therefore you must also release that under
the GPL when a user asks for all your SANE derived code. The same
would be true for any other backends that you looked at or borrowed
from.

allan
-- 
The truth is an offense, but not a sin

[sane-devel] Avision.c copyrights

2009-01-27 Thread Paul Fox

m. allan noah wrote:
  On Tue, Jan 27, 2009 at 1:56 PM, Ed Hamrick EdHamrick at aol.com wrote:
   I've asked him to release the source code to avision.c, and
   I'm waiting to see it.  I want to see how he got the Xerox
   DocuMate 150 working in avision.c.  I don't have one, and
   one of my customers wants to use it with VueScan.
  
  
  A reasonable request, however it makes your Avision support code a
  derivative of of SANE, and therefore you must also release that under
  the GPL when a user asks for all your SANE derived code. The same
  would be true for any other backends that you looked at or borrowed
  from.

looked at?  i don't believe that's true.  that implies there's
some sort of unpublished trade secret in play.  copyright applies
to expression, not concept.

paul
=-
 paul fox, pgf at foxharp.boston.ma.us (arlington, ma, where it's 25.3 degrees)

[sane-devel] Avision.c copyrights