Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #171092 > unrolled thread

Re: Compiling Canon LiDE 220 driver from source

Back to article view | Back to linux.debian.user

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Re: Compiling Canon LiDE 220 driver from source didier gaumet <didier.gaumet@gmail.com> - 2016-08-15 10:00 +0200
    Re: Compiling Canon LiDE 220 driver from source Lisi Reisz <lisi.reisz@gmail.com> - 2016-08-15 12:50 +0200
      Re: Compiling Canon LiDE 220 driver from source didier gaumet <didier.gaumet@gmail.com> - 2016-08-15 14:30 +0200
        Re: Compiling Canon LiDE 220 driver from source Lisi Reisz <lisi.reisz@gmail.com> - 2016-08-15 15:30 +0200
        Re: Compiling Canon LiDE 220 driver from source Brian <ad44@cityscape.co.uk> - 2016-08-15 15:30 +0200
          Re: Compiling Canon LiDE 220 driver from source didier gaumet <didier.gaumet@gmail.com> - 2016-08-15 15:50 +0200
            Re: Compiling Canon LiDE 220 driver from source Brian <ad44@cityscape.co.uk> - 2016-08-15 18:40 +0200
          Re: Compiling Canon LiDE 220 driver from source Lisi Reisz <lisi.reisz@gmail.com> - 2016-08-15 20:10 +0200
            Re: Compiling Canon LiDE 220 driver from source Brian <ad44@cityscape.co.uk> - 2016-08-15 20:50 +0200
          Re: Compiling Canon LiDE 220 driver from source Lisi Reisz <lisi.reisz@gmail.com> - 2016-08-16 14:00 +0200
            Re: Compiling Canon LiDE 220 driver from source didier gaumet <didier.gaumet@gmail.com> - 2016-08-16 14:40 +0200
            Re: Compiling Canon LiDE 220 driver from source Brian <ad44@cityscape.co.uk> - 2016-08-16 15:00 +0200
              Re: Compiling Canon LiDE 220 driver from source Lisi Reisz <lisi.reisz@gmail.com> - 2016-08-16 16:40 +0200
                Re: Compiling Canon LiDE 220 driver from source Brian <ad44@cityscape.co.uk> - 2016-08-16 18:30 +0200
                  Re: Compiling Canon LiDE 220 driver from source Lisi Reisz <lisi.reisz@gmail.com> - 2016-08-16 21:10 +0200
                  Re: Compiling Canon LiDE 220 driver from source Lisi Reisz <lisi.reisz@gmail.com> - 2016-08-16 23:50 +0200
                    Re: Compiling Canon LiDE 220 driver from source Brian <ad44@cityscape.co.uk> - 2016-08-17 00:20 +0200

#171092 — Re: Compiling Canon LiDE 220 driver from source

Le 15/08/2016 à 00:13, Lisi Reisz a écrit :
> Although Canon LiDE 220 
[...]
> lisi@Eros:~$ lsusb | grep Canon
> Bus 001 Device 003: ID 04a9:190f Canon, Inc.
> lisi@Eros:~$ grep 190f /etc/sane.d/genesys.conf
> 
> Having little faith, I cat-ed /etc/sane.d/genesys.conf, and the 220 driver was 
> indeed not there.
[...]

I verified: though the Canon LiDE 220 scanner is not listed in
/etc/sane.d/genesys.conf of libsane-common 1.0.24-8+deb8u1 (jessie), it
is in version 1.0.25-2 (stretch) of this package:

# Canon LiDE 220
usb 0x04a9 0x190f

[toc] | [next] | [standalone]

#171098

On Monday 15 August 2016 08:52:15 didier gaumet wrote:
> Le 15/08/2016 à 00:13, Lisi Reisz a écrit :
> > Although Canon LiDE 220
>
> [...]
>
> > lisi@Eros:~$ lsusb | grep Canon
> > Bus 001 Device 003: ID 04a9:190f Canon, Inc.
> > lisi@Eros:~$ grep 190f /etc/sane.d/genesys.conf
> >
> > Having little faith, I cat-ed /etc/sane.d/genesys.conf, and the 220
> > driver was indeed not there.
>
> [...]
>
> I verified: though the Canon LiDE 220 scanner is not listed in
> /etc/sane.d/genesys.conf of libsane-common 1.0.24-8+deb8u1 (jessie), it
> is in version 1.0.25-2 (stretch) of this package:
>
> # Canon LiDE 220
> usb 0x04a9 0x190f

Thanks, didier.  That is nice to know.

So it should be in the up-to-date tar ball, if I were to succeed in sorting 
that out.  But are you suggesting that I would do better to backport from 
Stretch?  I had decided that the tar ball would be simpler and more sure.  
But perhaps now is the time to learn to backport!!

Lisi

[toc] | [prev] | [next] | [standalone]

#171099

Le 15/08/2016 à 12:42, Lisi Reisz a écrit :

> Thanks, didier.  That is nice to know.
> 
> So it should be in the up-to-date tar ball, if I were to succeed in sorting 
> that out.  But are you suggesting that I would do better to backport from 
> Stretch?  I had decided that the tar ball would be simpler and more sure.  
> But perhaps now is the time to learn to backport!!
> 
> Lisi

being lazy nowadays, if possible I avoid any source code compilation ;-)

libsane-common unavailable in backports, I don't know if this could be
profitable to you to backport it yourself.

you could test a stable/testing mix in your sources.list with pinning
preferences to follow sane in testing.
or you could stay stable and try a quick and dirty trick in jessie by
jnserting:

# Canon LiDE 220
usb 0x04a9 0x190f

in your /etc/sane.d/genesys.conf: I don't know how is designed the
genesys backend, so maybe it is sufficient to obtain a functionning
scanner, minus the LiDE220 specificities?

[toc] | [prev] | [next] | [standalone]

#171102

On Monday 15 August 2016 13:23:36 didier gaumet wrote:
> Le 15/08/2016 à 12:42, Lisi Reisz a écrit :
> > Thanks, didier.  That is nice to know.
> >
> > So it should be in the up-to-date tar ball, if I were to succeed in
> > sorting that out.  But are you suggesting that I would do better to
> > backport from Stretch?  I had decided that the tar ball would be simpler
> > and more sure. But perhaps now is the time to learn to backport!!
> >
> > Lisi
>
> being lazy nowadays, if possible I avoid any source code compilation ;-)
>
> libsane-common unavailable in backports, I don't know if this could be
> profitable to you to backport it yourself.
>
> you could test a stable/testing mix in your sources.list with pinning
> preferences to follow sane in testing.
> or you could stay stable and try a quick and dirty trick in jessie by
> jnserting:
>
> # Canon LiDE 220
> usb 0x04a9 0x190f
>
> in your /etc/sane.d/genesys.conf: I don't know how is designed the
> genesys backend, so maybe it is sufficient to obtain a functionning
> scanner, minus the LiDE220 specificities?

Thanks for the suggestions.  The last didn't work. :-(  I'll try the other 
two - not simultaneously!  

Lisi

[toc] | [prev] | [next] | [standalone]

#171103

On Mon 15 Aug 2016 at 14:23:36 +0200, didier gaumet wrote:

> Le 15/08/2016 à 12:42, Lisi Reisz a écrit :
> 
> > Thanks, didier.  That is nice to know.
> > 
> > So it should be in the up-to-date tar ball, if I were to succeed in sorting 
> > that out.  But are you suggesting that I would do better to backport from 
> > Stretch?  I had decided that the tar ball would be simpler and more sure.  
> > But perhaps now is the time to learn to backport!!
> > 
> > Lisi
> 
> being lazy nowadays, if possible I avoid any source code compilation ;-)
> 
> libsane-common unavailable in backports, I don't know if this could be
> profitable to you to backport it yourself.

A good guide to backporting is at

  https://raphaelhertzog.com/2010/12/15/howto-to-rebuild-debian-packages/

A deb-src line in sources.list for unstable is needed to do

  apt-get source libsane-common/unstable

Then

  apt-get build-deps libsane-common/unstable

should get the dependencies from stable to build libsane-common and
libsane.
 
> you could test a stable/testing mix in your sources.list with pinning
> preferences to follow sane in testing.
> or you could stay stable and try a quick and dirty trick in jessie by
> jnserting:
> 
> # Canon LiDE 220
> usb 0x04a9 0x190f
> 
> in your /etc/sane.d/genesys.conf: I don't know how is designed the
> genesys backend, so maybe it is sufficient to obtain a functionning
> scanner, minus the LiDE220 specificities?

I reckon the second approach will not work because the libraries need
an adjustment too.

[toc] | [prev] | [next] | [standalone]

#171104

Le 15/08/2016 à 15:25, Brian a écrit :
[...]
> I reckon the second approach will not work because the libraries need
> an adjustment too.

I plead guilty: Lisi just confirmed your point of view, In computer
science, crime (of lazyness) does not (always) pay ;-)

thanks for your input, Brian, I did not realize building a backport
package from source in Debian is so simple

[toc] | [prev] | [next] | [standalone]

#171110

On Mon 15 Aug 2016 at 15:47:00 +0200, didier gaumet wrote:

> Le 15/08/2016 à 15:25, Brian a écrit :
> [...]
> > I reckon the second approach will not work because the libraries need
> > an adjustment too.
> 
> I plead guilty: Lisi just confirmed your point of view, In computer
> science, crime (of lazyness) does not (always) pay ;-)
> 
> thanks for your input, Brian, I did not realize building a backport
> package from source in Debian is so simple

There is a simplicity to the process but how straightforward it is to
get to the destination of a new debian package depends on the package
being backported. libsane-common should give no trouble but chromium,
for example, requires build dependencies which are not in stable. And
the dependencies need dependencies, all of which have to be backported!

[toc] | [prev] | [next] | [standalone]

#171112

On Monday 15 August 2016 14:25:58 Brian wrote:
> A good guide to backporting is at
>
>   https://raphaelhertzog.com/2010/12/15/howto-to-rebuild-debian-packages/
>
> A deb-src line in sources.list for unstable is needed to do
>
>   apt-get source libsane-common/unstable
>
> Then
>
>   apt-get build-deps libsane-common/unstable
>
> should get the dependencies from stable to build libsane-common and
> libsane.
>  

Thank you, Brian.  That sounds great.  

I had been following this (mutatis mutandis)
https://wiki.debian.org/SimpleBackportCreation
but had got stuck on
https://wiki.debian.org/SimpleBackportCreation#Find_and_Install_missing_build_dependencies_as__found_in_debian.2Fcontrol
And went to do other jobs before tackling it again, and googling as neccesary. 

Yours sounds much simpler.  libsane-common doesn't seem to have many 
dependencies, but I though I mighty have to backport the whole of 
sane-backends, largely because I was a bit at sea.

I'll try later and report back.  

Why does one use Sid when the package is available in Stretch??

Lisi

[toc] | [prev] | [next] | [standalone]

#171114

On Mon 15 Aug 2016 at 19:05:55 +0100, Lisi Reisz wrote:

> On Monday 15 August 2016 14:25:58 Brian wrote:
> > A good guide to backporting is at
> >
> >   https://raphaelhertzog.com/2010/12/15/howto-to-rebuild-debian-packages/
> >
> > A deb-src line in sources.list for unstable is needed to do
> >
> >   apt-get source libsane-common/unstable
> >
> > Then
> >
> >   apt-get build-deps libsane-common/unstable
> >
> > should get the dependencies from stable to build libsane-common and
> > libsane.
> >  
> 
> Thank you, Brian.  That sounds great.  
> 
> I had been following this (mutatis mutandis)
> https://wiki.debian.org/SimpleBackportCreation

I haven't tested the method on that page extensively but a first glance
seems to indicate there is a missing step or two. Don't take this as
gospel though.

> but had got stuck on
> https://wiki.debian.org/SimpleBackportCreation#Find_and_Install_missing_build_dependencies_as__found_in_debian.2Fcontrol
> And went to do other jobs before tackling it again, and googling as neccesary. 
> 
> Yours sounds much simpler.  libsane-common doesn't seem to have many 
> dependencies, but I though I mighty have to backport the whole of 
> sane-backends, largely because I was a bit at sea.

  apt-get source libsane-common/testing

actually downloads the sane-backends source package.

> I'll try later and report back.  

My report is that backporting libsame-common works for me. I cannot
instill more confidence than that. :)

> Why does one use Sid when the package is available in Stretch??

By all means replace unstable with testing in the commands I gave. I
tend to use unstable because it is the latest and, in any case, testing
has the same version for the source package, so it doesn't matter.

[toc] | [prev] | [next] | [standalone]

#171138

On Monday 15 August 2016 14:25:58 Brian wrote:
> On Mon 15 Aug 2016 at 14:23:36 +0200, didier gaumet wrote:
> > Le 15/08/2016 à 12:42, Lisi Reisz a écrit :
> > > Thanks, didier.  That is nice to know.
> > >
> > > So it should be in the up-to-date tar ball, if I were to succeed in
> > > sorting that out.  But are you suggesting that I would do better to
> > > backport from Stretch?  I had decided that the tar ball would be
> > > simpler and more sure. But perhaps now is the time to learn to
> > > backport!!
> > >
> > > Lisi
> >
> > being lazy nowadays, if possible I avoid any source code compilation ;-)
> >
> > libsane-common unavailable in backports, I don't know if this could be
> > profitable to you to backport it yourself.
>
> A good guide to backporting is at
>
>   https://raphaelhertzog.com/2010/12/15/howto-to-rebuild-debian-packages/
>
> A deb-src line in sources.list for unstable is needed to do
>
>   apt-get source libsane-common/unstable
>
> Then
>
>   apt-get build-deps libsane-common/unstable
>
> should get the dependencies from stable to build libsane-common and
> libsane.

I have got stuck.  Only slightly further on than I had already got stuck.  
(apt-get said it wasn't downloading what I had already downloaded!)

root@Eros:/home/lisi/Sane-Files# apt-get build-deps libsane-common/testing
E: Invalid operation build-deps
root@Eros:/home/lisi/Sane-Files# dpkg-checkbuilddeps.
bash: dpkg-checkbuilddeps.: command not found
root@Eros:/home/lisi/Sane-Files# aptitude show apt
Package: apt
Essential: yes
State: installed
Automatically installed: no
Version: 1.0.9.8.3

And somewhere while googling (I can't find it again!) I saw that build-deps is 
only in apt >= to 0.5.  So I should have it.

I'm going to go and get lunch. :-( I have an invalid husband.  The last thing 
I need is him back in hospital.

Thanks for the help.  I'll google some more after lunch.

Lisi
>
> > you could test a stable/testing mix in your sources.list with pinning
> > preferences to follow sane in testing.
> > or you could stay stable and try a quick and dirty trick in jessie by
> > jnserting:
> >
> > # Canon LiDE 220
> > usb 0x04a9 0x190f
> >
> > in your /etc/sane.d/genesys.conf: I don't know how is designed the
> > genesys backend, so maybe it is sufficient to obtain a functionning
> > scanner, minus the LiDE220 specificities?
>
> I reckon the second approach will not work because the libraries need
> an adjustment too.

[toc] | [prev] | [next] | [standalone]

#171139

Le 16/08/2016 à 13:57, Lisi Reisz a écrit :

> I have got stuck.  Only slightly further on than I had already got stuck.  
> (apt-get said it wasn't downloading what I had already downloaded!)
> 
> root@Eros:/home/lisi/Sane-Files# apt-get build-deps libsane-common/testing
> E: Invalid operation build-deps
[...]

build-dep without s :-)

[toc] | [prev] | [next] | [standalone]

#171141

On Tue 16 Aug 2016 at 12:57:50 +0100, Lisi Reisz wrote:

> On Monday 15 August 2016 14:25:58 Brian wrote:
> >
> > A good guide to backporting is at
> >
> >   https://raphaelhertzog.com/2010/12/15/howto-to-rebuild-debian-packages/
> >
> > A deb-src line in sources.list for unstable is needed to do
> >
> >   apt-get source libsane-common/unstable
> >
> > Then
> >
> >   apt-get build-deps libsane-common/unstable
> >
> > should get the dependencies from stable to build libsane-common and
> > libsane.
> 
> I have got stuck.  Only slightly further on than I had already got stuck.  
> (apt-get said it wasn't downloading what I had already downloaded!)
> 
> root@Eros:/home/lisi/Sane-Files# apt-get build-deps libsane-common/testing
> E: Invalid operation build-deps

Mea culpa. Please see the apt-get manual: build-dep (no "s").

[toc] | [prev] | [next] | [standalone]

#171143

On Tuesday 16 August 2016 13:49:48 Brian wrote:
> On Tue 16 Aug 2016 at 12:57:50 +0100, Lisi Reisz wrote:
> > On Monday 15 August 2016 14:25:58 Brian wrote:
> > > A good guide to backporting is at
> > >
> > >  
> > > https://raphaelhertzog.com/2010/12/15/howto-to-rebuild-debian-packages/
> > >
> > > A deb-src line in sources.list for unstable is needed to do
> > >
> > >   apt-get source libsane-common/unstable
> > >
> > > Then
> > >
> > >   apt-get build-deps libsane-common/unstable
> > >
> > > should get the dependencies from stable to build libsane-common and
> > > libsane.
> >
> > I have got stuck.  Only slightly further on than I had already got stuck.
> > (apt-get said it wasn't downloading what I had already downloaded!)
> >
> > root@Eros:/home/lisi/Sane-Files# apt-get build-deps
> > libsane-common/testing E: Invalid operation build-deps
>
> Mea culpa. Please see the apt-get manual: build-dep (no "s").

Thanks, both. :-)

Everything now built, though there was an error at the end:

Now running lintian...
warning: the authors of lintian do not recommend running it with root 
privileges!
W: libsane: package-name-doesnt-match-sonames libsane1
N: 2 tags overridden (1 error, 1 warning)
Finished running lintian.
root@Eros:/home/lisi/Sane-Files/sane-backends-1.0.25# 

And although sane-find-scanner continued to be able to see the scanner, 
scanimage -L continues determinedly not to see it.

The Canon LiDE 220 is explicitly mentioned as being supported in the file 
sane-genesys.5, which is in /etc/sane.d

So it is there.  Somewhere.  But not being found.  There is a lot of gumph 
there from my various efforts, and I am afraid of just deleting anything 
because I don't know what should be there!

I haven't googled much yet.  My husband is asking why I don't just upgrade to 
Stretch.  Good question!!  But this should be soluble reasonably easily.

Lisi

[toc] | [prev] | [next] | [standalone]

#171144

On Tue 16 Aug 2016 at 15:39:00 +0100, Lisi Reisz wrote:

> On Tuesday 16 August 2016 13:49:48 Brian wrote:
> >
> > Mea culpa. Please see the apt-get manual: build-dep (no "s").
> 
> Thanks, both. :-)
> 
> Everything now built, though there was an error at the end:
> 
> Now running lintian...
> warning: the authors of lintian do not recommend running it with root 
> privileges!

You built the packages as root? Lintian would then run as root. There is
a warning about this. Can be ignored but 'debuild -us -uc' should be run
as a user.

> W: libsane: package-name-doesnt-match-sonames libsane1
> N: 2 tags overridden (1 error, 1 warning)
> Finished running lintian.
> root@Eros:/home/lisi/Sane-Files/sane-backends-1.0.25# 

Probably nothing to worry about when it comes to using sane. But I am no
expert here.

Five .debs are built; only libsane, libsane-common and sane-utils need
to be installed with 'dpkg -i'.
 
> And although sane-find-scanner continued to be able to see the scanner, 
> scanimage -L continues determinedly not to see it.
> 
> The Canon LiDE 220 is explicitly mentioned as being supported in the file 
> sane-genesys.5, which is in /etc/sane.d

At least 'sane-find-scanner' works. :) Note that its purpose is only to
find a scanner. The purpose of 'scanimage -L' is to discover whether
there is a backend which will drive the found scanner. As you say, it
should find yours is supported in genesys.conf.

Check that 0x04a9 0x1906 in genesys.conf is matched by what the output
of 'lsusb' should show (04a9 1906).

Make it easy for 'scanimage -L' and not have it have to search for a
backend to use: comment out or delete every line in dll.conf apart from
"genesys" and restart the sane service.

Change USB ports for the scanner. USB2 or USB3?

[toc] | [prev] | [next] | [standalone]

#171146

On Tuesday 16 August 2016 17:27:10 Brian wrote:
> Five .debs are built; only libsane, libsane-common and sane-utils need
> to be installed with 'dpkg -i'.

Ah!  I don't know about senior moments.  I need a rest, some sleep and a new 
brain.

Lisi

[toc] | [prev] | [next] | [standalone]

#171150

On Tuesday 16 August 2016 17:27:10 Brian wrote:
> On Tue 16 Aug 2016 at 15:39:00 +0100, Lisi Reisz wrote:
> > On Tuesday 16 August 2016 13:49:48 Brian wrote:
> > > Mea culpa. Please see the apt-get manual: build-dep (no "s").
> >
> > Thanks, both. :-)
> >
> > Everything now built, though there was an error at the end:
> >
> > Now running lintian...
> > warning: the authors of lintian do not recommend running it with root
> > privileges!
>
> You built the packages as root? Lintian would then run as root. There is
> a warning about this. Can be ignored but 'debuild -us -uc' should be run
> as a user.
>
> > W: libsane: package-name-doesnt-match-sonames libsane1
> > N: 2 tags overridden (1 error, 1 warning)
> > Finished running lintian.
> > root@Eros:/home/lisi/Sane-Files/sane-backends-1.0.25#
>
> Probably nothing to worry about when it comes to using sane. But I am no
> expert here.
>
> Five .debs are built; only libsane, libsane-common and sane-utils need
> to be installed with 'dpkg -i'.
>
> > And although sane-find-scanner continued to be able to see the scanner,
> > scanimage -L continues determinedly not to see it.
> >
> > The Canon LiDE 220 is explicitly mentioned as being supported in the file
> > sane-genesys.5, which is in /etc/sane.d
>
> At least 'sane-find-scanner' works. :) Note that its purpose is only to
> find a scanner. The purpose of 'scanimage -L' is to discover whether
> there is a backend which will drive the found scanner. As you say, it
> should find yours is supported in genesys.conf.
>
> Check that 0x04a9 0x1906 in genesys.conf is matched by what the output
> of 'lsusb' should show (04a9 1906).
>
> Make it easy for 'scanimage -L' and not have it have to search for a
> backend to use: comment out or delete every line in dll.conf apart from
> "genesys" and restart the sane service.
>
> Change USB ports for the scanner. USB2 or USB3?

After a lot more wrong turnings and much agonising, thinking instead of 
panicking (at last!) and retrying:

root@Eros:/home/lisi/Sane-Files# scanimage -L
device `genesys:libusb:001:003' is a Canon LiDE 220 flatbed scanner
root@Eros:/home/lisi/Sane-Files#  

Thank you so much Brian and didier, especially for your patience.

Lisi

[toc] | [prev] | [next] | [standalone]

#171151

On Tue 16 Aug 2016 at 22:45:29 +0100, Lisi Reisz wrote:

[...Snip... The history is in previous mails].

> After a lot more wrong turnings and much agonising, thinking instead of 
> panicking (at last!) and retrying:
> 
> root@Eros:/home/lisi/Sane-Files# scanimage -L
> device `genesys:libusb:001:003' is a Canon LiDE 220 flatbed scanner
> root@Eros:/home/lisi/Sane-Files#  
> 
> Thank you so much Brian and didier, especially for your patience.

A splendid outcome and a victory for backporting! Thank you for the
feedback and sticking with it until the end.

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web