Re: [sane-devel] Support for Epson WorkForce ES-200 on Linux Mint 18.2

[Olaf Meeuwissen]

Hi Alkarim,

Alkarim Kanji writes:

> I could not find the pager section in README.rst file. I searched manually
> and electronically.
>
> My understanding of pager README.rst is "pager" section in the README.rst
> file that is part of the "imagescan-bundle-linuxmint-18-1.3.23.x64.deb
> folder."

Sorry for not being clear.  `pager` is a command that shows you the
content of the README.rst file.  You may be more familiar with `more` or
`less`.  Anyway, just read the README.rst file.

Hope this helps,
--
Olaf Meeuwissen, LPIC-2FSF Associate Member since 2004-01-27
 GnuPG key: F84A2DD9/B3C0 2F47 EA19 64F4 9F13  F43E B8A4 A88A F84A 2DD9
 Support Free Softwarehttps://my.fsf.org/donate
 Join the Free Software Foundation  https://my.fsf.org/join

-- 
sane-devel mailing list: sane-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
Unsubscribe: Send mail with subject "unsubscribe your_password"
 to sane-devel-requ...@lists.alioth.debian.org

Re: [sane-devel] Support for Epson WorkForce ES-200 on Linux Mint 18.2

[Alkarim Kanji]

I could not find the pager section in README.rst file. I searched manually
and electronically.

My understanding of pager README.rst is "pager" section in the README.rst
file that is part of the "imagescan-bundle-linuxmint-18-1.3.23.x64.deb
folder."


---
Use the free, legal, and versatile office software suite: LibreOffice
.

On Sat, Jan 27, 2018 at 9:37 PM, Olaf Meeuwissen 
wrote:

> Hi,
>
> Cc:ing sane-devel again to keep everyone informed.
>
> Alkarim Kanji writes:
>
> > Thank you for the support, Olaf.
> >
> > When I first started attempting to download drivers/software, I ran into
> > the " http://support.epson.net/linux/en/imagescanv3.php?
> > version=1.3.23#linux_mint" file you pointed to in your email.  I even
> > extracted it (within the downloads folder), but got error messages when
> > attempting to use the commands given in the README.rst file.  I guess
> where
> > I am going wrong is extraction: should I be extracting the zip file to
> > another folder (as opposed to download subfolders)?  If yes, which folder
> > should I be extracting it to?  I was unable to find an appropriate
> folder.
> >
> > I would appreciated a little more detail.  Below I have shared the error
> > messages I am getting so you can guide me accordingly.
> >
> > When I extract the zipped
> > "imagescan-bundle-linuxmint-18-1.3.23.x64.deb.tar.gz" folder (which
> > downloads when I click the link above), I get a folder called,
> > "imagescan-bundle-linuxmint-18-1.3.23.x64.deb"  I then right-clicked the
> > "imagescan-bundle-linuxmint-18-1.3.23.x64.deb" folder and selected the
> > option to open Terminal.  In Terminal, I gave the command, "tar xaf
> > imagescan-bundle-linuxmint-18-1.3.23.x64.deb.tar.gz" (as prescribed in
> the
> > README.rst file), which resulted in the following error message:
> >
> > imagescan-bundle-linuxmint-18-1.3.23.x64.deb.tar.gz: Cannot open: No
> such
> > file or directory
> > tar: Error is not recoverable: exiting now
> >
> > Where am I going wrong?
>
> OK, I see.  You used some GUI application to extract and navigate to the
> folder that that created.  In that case you can continue with
>
>   pager README.rst
>
> and follow the directions in there to get up and running.
>
> Hope that helps,
> --
> Olaf Meeuwissen, LPIC-2FSF Associate Member since 2004-01-27
>  GnuPG key: F84A2DD9/B3C0 2F47 EA19 64F4 9F13  F43E B8A4 A88A F84A 2DD9
>  Support Free Softwarehttps://my.fsf.org/donate
>  Join the Free Software Foundation  https://my.fsf.org/join
>
-- 
sane-devel mailing list: sane-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
Unsubscribe: Send mail with subject "unsubscribe your_password"
 to sane-devel-requ...@lists.alioth.debian.org

Re: [sane-devel] Support for Epson WorkForce ES-200 on Linux Mint 18.2

[Olaf Meeuwissen]

Hi,

Cc:ing sane-devel again to keep everyone informed.

Alkarim Kanji writes:

> Thank you for the support, Olaf.
>
> When I first started attempting to download drivers/software, I ran into
> the " http://support.epson.net/linux/en/imagescanv3.php?
> version=1.3.23#linux_mint" file you pointed to in your email.  I even
> extracted it (within the downloads folder), but got error messages when
> attempting to use the commands given in the README.rst file.  I guess where
> I am going wrong is extraction: should I be extracting the zip file to
> another folder (as opposed to download subfolders)?  If yes, which folder
> should I be extracting it to?  I was unable to find an appropriate folder.
>
> I would appreciated a little more detail.  Below I have shared the error
> messages I am getting so you can guide me accordingly.
>
> When I extract the zipped
> "imagescan-bundle-linuxmint-18-1.3.23.x64.deb.tar.gz" folder (which
> downloads when I click the link above), I get a folder called,
> "imagescan-bundle-linuxmint-18-1.3.23.x64.deb"  I then right-clicked the
> "imagescan-bundle-linuxmint-18-1.3.23.x64.deb" folder and selected the
> option to open Terminal.  In Terminal, I gave the command, "tar xaf
> imagescan-bundle-linuxmint-18-1.3.23.x64.deb.tar.gz" (as prescribed in the
> README.rst file), which resulted in the following error message:
>
> imagescan-bundle-linuxmint-18-1.3.23.x64.deb.tar.gz: Cannot open: No such
> file or directory
> tar: Error is not recoverable: exiting now
>
> Where am I going wrong?

OK, I see.  You used some GUI application to extract and navigate to the
folder that that created.  In that case you can continue with

  pager README.rst

and follow the directions in there to get up and running.

Hope that helps,
--
Olaf Meeuwissen, LPIC-2FSF Associate Member since 2004-01-27
 GnuPG key: F84A2DD9/B3C0 2F47 EA19 64F4 9F13  F43E B8A4 A88A F84A 2DD9
 Support Free Softwarehttps://my.fsf.org/donate
 Join the Free Software Foundation  https://my.fsf.org/join

-- 
sane-devel mailing list: sane-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
Unsubscribe: Send mail with subject "unsubscribe your_password"
 to sane-devel-requ...@lists.alioth.debian.org

Re: [sane-devel] [janitorial] Relocating the SANE Project

[Olaf Meeuwissen]

Hi Markus,

Markus Heiser writes:

>> Am 26.01.2018 um 09:59 schrieb Olaf Meeuwissen :
>>
>> Dear all,
>>
>> TL;DR :: Let's move to GitLab.com!  Mailing list TBD.
>
> [ ... ]
>
>> The idea of putting a repository mirror on GitHub is interesting but I'm
>> not sure how pull requests and issues would work out if things are split
>> over multiple sites.
>
> Its not a show stopper: pull request can be handled by git itself,
> adding the github remote repo and pull the feature branch from there
> into the gitlab origin. Vice versa the github users are be able to
> fork from gitlab origin this way.
>
>  What I mean: there is no need for a github mirror.
>
> Stay with a Single-Point-of-Definition and do not mirror, it will
> only confuse the github users.

Thanks for your comments.  I realize that a github mirror is not
required.  It's just something I hadn't considered.  When I did, I
started to wonder how the web based merge/pull request workflows would
interoperate.  I have the impression that it will be confusing at the
very least, so, yes, let's start with a *single* location for the
project, at least until we're all settled on GitLab.com

Again, thanks for the feedback,
--
Olaf Meeuwissen, LPIC-2FSF Associate Member since 2004-01-27
 GnuPG key: F84A2DD9/B3C0 2F47 EA19 64F4 9F13  F43E B8A4 A88A F84A 2DD9
 Support Free Softwarehttps://my.fsf.org/donate
 Join the Free Software Foundation  https://my.fsf.org/join

-- 
sane-devel mailing list: sane-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
Unsubscribe: Send mail with subject "unsubscribe your_password"
 to sane-devel-requ...@lists.alioth.debian.org

Re: [sane-devel] hosts.resolv ???

[Olaf Meeuwissen]

Hi,

ToddAndMargo writes:

> Hi All,
>
> Fedora 27
>
> $ rpm -qa sane\*
> sane-backends-1.0.27-9.fc27.x86_64
> sane-backends-drivers-scanners-1.0.27-9.fc27.x86_64
> sane-backends-drivers-cameras-1.0.27-9.fc27.i686
> sane-backends-libs-1.0.27-9.fc27.i686
> sane-backends-daemon-1.0.27-9.fc27.x86_64
> sane-backends-drivers-scanners-1.0.27-9.fc27.i686
> sane-backends-libs-1.0.27-9.fc27.x86_64
> sane-backends-drivers-cameras-1.0.27-9.fc27.x86_64
>
> What I am trying to do is to allow everyone of
> 192.168.255.0/24   and
> 127.0.0.1
>
> to access saned
>
> as such I have /etc/sane.d/saned.conf (comments removed):
>
> 192.168.255.0/24
> 127.0.0.1
>
> Have I done things correct so far?
>
> Confusion:  in the saned man page, it states:
>
>  FILES
> /etc/hosts.equiv
> The  hosts listed in this file are permitted to
> access all local SANE devices.  Caveat: this
> file imposes serious security risks and its
> use is not recommended.
>
> No fooling not recommended!
>
> Why do I need hosts.equiv to allow access to all SANE
> devices?  I though I just did that in saned.conf?

You don't need one.  Just use /etc/sane.d/saned.conf.  The manual page
is just saying saned will use /etc/hosts.equiv if present.  You are
safer of without a hosts.equiv file.  For details see

  http://man7.org/linux/man-pages/man5/hosts.equiv.5.html

Hope this helps,
--
Olaf Meeuwissen, LPIC-2FSF Associate Member since 2004-01-27
 GnuPG key: F84A2DD9/B3C0 2F47 EA19 64F4 9F13  F43E B8A4 A88A F84A 2DD9
 Support Free Softwarehttps://my.fsf.org/donate
 Join the Free Software Foundation  https://my.fsf.org/join

-- 
sane-devel mailing list: sane-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
Unsubscribe: Send mail with subject "unsubscribe your_password"
 to sane-devel-requ...@lists.alioth.debian.org

Re: [sane-devel] PIXMA backend Canon i-SENSYS MF633cdw Support

[Wojciech Teichert]

scanimage -V
scanimage (sane-backends) 1.0.27git; backend version 1.0.27


2018-01-27 9:57 GMT+01:00 Rolf Bensch :

> Hi Wojciech,
>
> Please check the version of SANE you are using:
> $ scanimage -V
>
> How did you connect your scanner? For testing it should connected on an
> USB port.
>
> A remark to your installation: Please remove your self compiled SANE from
> your system and follow the install description from the file INSTALL.linux,
> which comes with the sources.
>
> Hope this helps.
>
> Cheers,
> Rolf
>
> Am 23.01.2018 um 12:46 schrieb Wojciech Teichert:
>
> pixma.log have one line: scanimage: no SANE devices found
>
> 2018-01-22 19:34 GMT+01:00 Rolf Bensch :
>
>> Hi Wojciech,
>>
>> Please provide a logfile created with:
>>
>> $ SANE_DEBUG_PIXMA=4 scanimage 2> pixma.log > pixma.pnm
>>
>> Please zip, tar.gz or 7zip pixma.log and send it to me.
>>
>> Cheers,
>> Rolf
>>
>> Am 22.01.2018 um 03:29 schrieb Wojciech Teichert:
>>
>>  scanimage -L
>>
>> No scanners were identified. If you were expecting something different,
>> check that the scanner is plugged in, turned on and detected by the
>> sane-find-scanner tool (if appropriate). Please read the documentation
>> which came with this software (README, FAQ, manpages).
>> root@### sane-find-scanner
>>
>>   # sane-find-scanner will now attempt to detect your scanner. If the
>>   # result is different from what you expected, first make sure your
>>   # scanner is powered up and properly connected to your computer.
>>
>>   # No SCSI scanners found. If you expected something different, make
>> sure that
>>   # you have loaded a kernel SCSI driver for your SCSI adapter.
>>
>> found USB scanner (vendor=0x04a9 [Canon], product=0x27e1 [MF633C/635C])
>> at libusb:001:005
>>   # Your USB scanner was (probably) detected. It may or may not be
>> supported by
>>   # SANE. Try scanimage -L and read the backend's manpage.
>>
>>   # Not checking for parallel port scanners.
>>
>>   # Most Scanners connected to the parallel port or other proprietary
>> ports
>>   # can't be detected by this program.
>> root@### scanimage -L
>>
>> No scanners were identified. If you were expecting something different,
>> check that the scanner is plugged in, turned on and detected by the
>> sane-find-scanner tool (if appropriate). Please read the documentation
>> which came with this software (README, FAQ, manpages)
>>
>> This is new version from git://git.debian.org/sane/sane-backends.git
>> using ./configure --prefix=/usr --libdir=/usr/lib/x86_64-linux-gnu
>> --sysconfdir=/etc --localstatedir=/var --enable-avahi && make -j4
>>
>> 2018-01-03 21:09 GMT+01:00 Rolf Bensch :
>>
>>> Hi Wojtek,
>>>
>>> I just added your scanner to SANE. Please check out the recent version
>>> from git or you can use the daily git snapshot tomorrow.
>>>
>>> Please report if all scanning features (75-600dpi, simple and duplex
>>> document feeder) are running with USB. After this you can try the bjnp
>>> interface.
>>>
>>> Hope this helps.
>>>
>>> Cheers,
>>> Rolf
>>>
>>>
>>> Am 13.12.2017 um 09:58 schrieb Wojtek Teichert:
>>> >  Can you add support for Canon i-SENSYS MF633cdw scanner?
>>>
>>>
>>
>>
>
>
-- 
sane-devel mailing list: sane-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
Unsubscribe: Send mail with subject "unsubscribe your_password"
 to sane-devel-requ...@lists.alioth.debian.org

[sane-devel] hosts.resolv ???

[ToddAndMargo]

Hi All,

Fedora 27

$ rpm -qa sane\*
sane-backends-1.0.27-9.fc27.x86_64
sane-backends-drivers-scanners-1.0.27-9.fc27.x86_64
sane-backends-drivers-cameras-1.0.27-9.fc27.i686
sane-backends-libs-1.0.27-9.fc27.i686
sane-backends-daemon-1.0.27-9.fc27.x86_64
sane-backends-drivers-scanners-1.0.27-9.fc27.i686
sane-backends-libs-1.0.27-9.fc27.x86_64
sane-backends-drivers-cameras-1.0.27-9.fc27.x86_64

What I am trying to do is to allow everyone of
   192.168.255.0/24   and
   127.0.0.1

to access saned

as such I have /etc/sane.d/saned.conf (comments removed):

192.168.255.0/24
127.0.0.1

Have I done things correct so far?

Confusion:  in the saned man page, it states:

FILES
   /etc/hosts.equiv
   The  hosts listed in this file are permitted to
   access all local SANE devices.  Caveat: this
   file imposes serious security risks and its
   use is not recommended.

No fooling not recommended!

Why do I need hosts.equiv to allow access to all SANE
devices?  I though I just did that in saned.conf?

Yours in confusion,
-T

--

Yesterday it worked.
Today it is not working.
Windows is like that.



--
sane-devel mailing list: sane-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
Unsubscribe: Send mail with subject "unsubscribe your_password"
to sane-devel-requ...@lists.alioth.debian.org

Re: [sane-devel] How can I help with Canon Maxify MB2000 series testing?

[Rolf Bensch]

Hi Patrick,

Please scan all scan options (color, grayscale, lineart, 75...600 dpi)
from flatbed.

Then test the document feeder with your preferred settings (e.g. A4, 300
dpi) and the whole sheet size. With a single sheet and multiple sheets.
At least test duplex scanning from ADF, single sheet and multiple sheets.

I'm getting the best ADF scan results with gscan2pdf (I really never got
best results using scanimage or xsane). For scanning single sheets from
flatbed or ADF (one side only) you can use your favorite frontend, e.g.
xsane.

If you might have problems, please test also connected with USB only.

Many thanks for report.

Cheers,
Rolf


Am 26.01.2018 um 00:33 schrieb Patrick Roncagliolo:
> I forgot to specify that obviously SANE driver worked and allowed me
> to do some scans with Xsane and ScanImage.
> My reference to ScanGearMP is simply for completeness, but does not
> relate with the main point of my previous mail.
>
> So, rephrasing:  "I can say LibSane works with MB2350 via LAN connection".
>
> Il giorno ven 26 gen 2018 alle ore 00:27 Patrick Roncagliolo
> > ha scritto:
>
> Hello, 
> I saw testers are needed for this series of scanners.
>
> I have a Canon Maxify MB2350 scanner, connected through LAN. 
> I can detect the scanner from Canon ScanGearMP 3.40 from Ubuntu
> Linux 16.04. 
> I added "bjnp://192.168.1.5 " to my pixma.conf
> file, where 192.168.1.5 is my scanner IP address.
> LibSane is taken from the daily git snapshots from RolfBensch's
> PPA (now: 1.0.27+git20180122).
>
> _I can say it works._ But I hope to help more if I can. So: is
> there a way to do something useful other than scanning a random
> sheet of paper? Do you have standard tests or data collection
> procedure that could help you to improve support or verify that
> all is working great? Do you need some packet sniffing or
> something like that?
>
> Best regards,
> Patrick Roncagliolo
>

-- 
sane-devel mailing list: sane-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
Unsubscribe: Send mail with subject "unsubscribe your_password"
 to sane-devel-requ...@lists.alioth.debian.org

Re: [sane-devel] /etc/sane.d/saned.conf vs /etc/saned.conf?

[ToddAndMargo]

On 01/27/2018 03:18 AM, Olaf Meeuwissen wrote:

Hi,

ToddAndMargo writes:


Hi All,

When configuring saned, what is the difference between the access
list in

/etc/sane.d/saned.conf

and

/etc/saned.conf


By default, saned looks for saned.conf in the directory that was
specified at build time.  For most Linux distributions this will be
/etc/sane.d, the result of passing a --configdir=/etc option to the
configure script (which tags the /sane.d part on by itself).

Using the *normal* build and install procedures that are part of
sane-backends, there is *no* way you would get an /etc/saned.conf.
Any chance you put this there yourself?

If you really want to use /etc/saned.conf, you need to use

   SANE_CONFIG_DIR=/etc saned ...

As far as file contents is concerned, both are processed in the same
way.  It only a matter of which one is used and, as said, the default
is to use the first.

Hope this helps,
--
Olaf Meeuwissen, LPIC-2FSF Associate Member since 2004-01-27
  GnuPG key: F84A2DD9/B3C0 2F47 EA19 64F4 9F13  F43E B8A4 A88A F84A 2DD9
  Support Free Softwarehttps://my.fsf.org/donate
  Join the Free Software Foundation  https://my.fsf.org/join




Thank you!  I will remove the /etc/saned one.

--
~~
Computers are like air conditioners.
They malfunction when you open windows
~~


--
sane-devel mailing list: sane-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
Unsubscribe: Send mail with subject "unsubscribe your_password"
to sane-devel-requ...@lists.alioth.debian.org

Re: [sane-devel] /etc/sane.d/saned.conf vs /etc/saned.conf?

[ToddAndMargo]

On 01/27/2018 03:18 AM, Olaf Meeuwissen wrote:

Hi,

ToddAndMargo writes:


Hi All,

When configuring saned, what is the difference between the access
list in

/etc/sane.d/saned.conf

and

/etc/saned.conf


By default, saned looks for saned.conf in the directory that was
specified at build time.  For most Linux distributions this will be
/etc/sane.d, the result of passing a --configdir=/etc option to the
configure script (which tags the /sane.d part on by itself).

Using the *normal* build and install procedures that are part of
sane-backends, there is *no* way you would get an /etc/saned.conf.
Any chance you put this there yourself?

If you really want to use /etc/saned.conf, you need to use

   SANE_CONFIG_DIR=/etc saned ...

As far as file contents is concerned, both are processed in the same
way.  It only a matter of which one is used and, as said, the default
is to use the first.

Hope this helps,


Hi Olaf,

What is this comment inside /etc/sane.d/saned.conf?

# NOTE: /etc/inetd.conf (or /etc/xinetd.conf) and
# /etc/services must also be properly configured to start
# the saned daemon as documented in saned(8), services(4)
# and inetd.conf(4) (or xinetd.conf(5)).

Why would I need both to get the saned daemon to work?

-T


--
sane-devel mailing list: sane-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
Unsubscribe: Send mail with subject "unsubscribe your_password"
to sane-devel-requ...@lists.alioth.debian.org

Re: [sane-devel] [janitorial] Relocating the SANE Project

[Paul Newall]

I'm afraid I don't have any useful knowledge on this subject, so very 
happy that someone is thinking about it.


Paul Newall


On 26/01/18 16:56, Jörn-Ingo Weigert wrote:
It's ok with me, having a well known and used interface for pull/merge 
requests and on top support for mobile in either web and app form, I 
do really appreciate. So let's go to girls.com ! 
*Backpack shouldered*


Am 26.01.2018 9:59 vorm. schrieb "Olaf Meeuwissen" 
>:


Dear all,

TL;DR :: Let's move to GitLab.com!  Mailing list TBD.

# Apologies for the belated follow-up.  I planned to wait a week or so
# to let the dust settle before following up but then Real Life got in
# the way :-(

Now for the long story,

On 2018-01-08, Olaf Meeuwissen (that's me!) wrote:

> [ ... Alioth will be discontinued sometime in 2018-05 ... so]
> the SANE Project will no longer be able to:
>
>  - communicate via the mailing lists
>  - push commits to its official git repositories
>  - update the bug and feature requests trackers
>  - update its website
>
> So we have to move some place else for our project hosting but
where?

I made a couple of suggestions and asked for feedback. Apart from one
off-list request to join the SANE project on GitLab.com, not one
of the
SANE developers has chimed in.  I will take that to mean that everyone
will be fine with whatever gets chosen in the end.  Speak up if that's
not the case!

The non-developers that did follow up mentioned[1] Sourceforge as a
possibility (and questioned[2] whether that was serious), offered help
with moving the mailing list to Debian infra-structure[1] (thanks,
btw!) and a preference for GitHub[3][4].

There was also a fairly detailed account[5] of the pros and cons of
GitLab vs. GitHub as well as an offer to host mailing lists[6].
Finally, there was a hint on how to get release notifications from
GitHub using an RSS feed[7].

There was the notion that GitLab/GitHub issues and merge/pull requests
could meaningfully replace a large part of the mailing
lists[3][5], yet
having mailing lists (archives) around would be nice. Several people
also pointed out that moving[4][5] and/or mirroring[3] git
repositories
elsewhere would be easy and that GitHub Pages have their "quirks"[5].
Finally, the fact that GitLab.com supports logging in via GitHub,
Google, Twitter and BitBucket accounts was pointed out as a pro[5].
Neither GitHub nor the Debian GitLab instance provide this
(although the
latter could, in theory).

 [1]:

https://lists.alioth.debian.org/pipermail/sane-devel/2018-January/035897.html


 [2]:

https://lists.alioth.debian.org/pipermail/sane-devel/2018-January/035900.html


 [3]:

https://lists.alioth.debian.org/pipermail/sane-devel/2018-January/035911.html


 [4]:

https://lists.alioth.debian.org/pipermail/sane-devel/2018-January/035898.html


 [5]:

https://lists.alioth.debian.org/pipermail/sane-devel/2018-January/035899.html


 [6]:

https://lists.alioth.debian.org/pipermail/sane-devel/2018-January/035921.html


 [7]:

https://lists.alioth.debian.org/pipermail/sane-devel/2018-January/035912.html



Taking this all in, and putting the mailing lists issue aside for
a bit,
I still prefer moving to GitLab.com.  In terms of repository,
issues and
merge/pull request support it offers pretty much the same as
GitHub, but
on top of that allows you to log in using accounts users may have with
(selected) other services.  This, I think, lowers the barrier to
report
issues.  Furthermore, GitLab.com comes with CI out-of-the-box
(which is
used already by the current *unofficial* mirror, btw!).

The idea of putting a repository mirror on GitHub is interesting
but I'm
not sure how pull requests and issues would work out if things are
split
over multiple sites.

Back to mailing lists, I think that for the short term making use
of the
Alioth mail continuation project[8] is our best alternative,
although I
am not exactly clear on that project's status.  If I understand things
correctly the current list maintainer will be asked to opt in before

Re: [sane-devel] /etc/sane.d/saned.conf vs /etc/saned.conf?

[Olaf Meeuwissen]

Hi,

ToddAndMargo writes:

> Hi All,
>
> When configuring saned, what is the difference between the access
> list in
>
> /etc/sane.d/saned.conf
>
> and
>
> /etc/saned.conf

By default, saned looks for saned.conf in the directory that was
specified at build time.  For most Linux distributions this will be
/etc/sane.d, the result of passing a --configdir=/etc option to the
configure script (which tags the /sane.d part on by itself).

Using the *normal* build and install procedures that are part of
sane-backends, there is *no* way you would get an /etc/saned.conf.
Any chance you put this there yourself?

If you really want to use /etc/saned.conf, you need to use

  SANE_CONFIG_DIR=/etc saned ...

As far as file contents is concerned, both are processed in the same
way.  It only a matter of which one is used and, as said, the default
is to use the first.

Hope this helps,
--
Olaf Meeuwissen, LPIC-2FSF Associate Member since 2004-01-27
 GnuPG key: F84A2DD9/B3C0 2F47 EA19 64F4 9F13  F43E B8A4 A88A F84A 2DD9
 Support Free Softwarehttps://my.fsf.org/donate
 Join the Free Software Foundation  https://my.fsf.org/join

-- 
sane-devel mailing list: sane-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
Unsubscribe: Send mail with subject "unsubscribe your_password"
 to sane-devel-requ...@lists.alioth.debian.org

[sane-devel] /etc/sane.d/saned.conf vs /etc/saned.conf?

[ToddAndMargo]

Hi All,

When configuring saned, what is the difference between the access
list in

/etc/sane.d/saned.conf

and

/etc/saned.conf


Many thanks,
-T


--
sane-devel mailing list: sane-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
Unsubscribe: Send mail with subject "unsubscribe your_password"
to sane-devel-requ...@lists.alioth.debian.org

Re: [sane-devel] [janitorial] Relocating the SANE Project

[Jörn-Ingo Weigert]

It's ok with me, having a well known and used interface for pull/merge
requests and on top support for mobile in either web and app form, I do
really appreciate. So let's go to girls.com! *Backpack shouldered*

Am 26.01.2018 9:59 vorm. schrieb "Olaf Meeuwissen" <
paddy-h...@member.fsf.org>:

> Dear all,
>
> TL;DR :: Let's move to GitLab.com!  Mailing list TBD.
>
> # Apologies for the belated follow-up.  I planned to wait a week or so
> # to let the dust settle before following up but then Real Life got in
> # the way :-(
>
> Now for the long story,
>
> On 2018-01-08, Olaf Meeuwissen (that's me!) wrote:
>
> > [ ... Alioth will be discontinued sometime in 2018-05 ... so]
> > the SANE Project will no longer be able to:
> >
> >  - communicate via the mailing lists
> >  - push commits to its official git repositories
> >  - update the bug and feature requests trackers
> >  - update its website
> >
> > So we have to move some place else for our project hosting but where?
>
> I made a couple of suggestions and asked for feedback.  Apart from one
> off-list request to join the SANE project on GitLab.com, not one of the
> SANE developers has chimed in.  I will take that to mean that everyone
> will be fine with whatever gets chosen in the end.  Speak up if that's
> not the case!
>
> The non-developers that did follow up mentioned[1] Sourceforge as a
> possibility (and questioned[2] whether that was serious), offered help
> with moving the mailing list to Debian infra-structure[1] (thanks,
> btw!) and a preference for GitHub[3][4].
>
> There was also a fairly detailed account[5] of the pros and cons of
> GitLab vs. GitHub as well as an offer to host mailing lists[6].
> Finally, there was a hint on how to get release notifications from
> GitHub using an RSS feed[7].
>
> There was the notion that GitLab/GitHub issues and merge/pull requests
> could meaningfully replace a large part of the mailing lists[3][5], yet
> having mailing lists (archives) around would be nice.  Several people
> also pointed out that moving[4][5] and/or mirroring[3] git repositories
> elsewhere would be easy and that GitHub Pages have their "quirks"[5].
> Finally, the fact that GitLab.com supports logging in via GitHub,
> Google, Twitter and BitBucket accounts was pointed out as a pro[5].
> Neither GitHub nor the Debian GitLab instance provide this (although the
> latter could, in theory).
>
>  [1]: https://lists.alioth.debian.org/pipermail/sane-devel/2018-
> January/035897.html
>  [2]: https://lists.alioth.debian.org/pipermail/sane-devel/2018-
> January/035900.html
>  [3]: https://lists.alioth.debian.org/pipermail/sane-devel/2018-
> January/035911.html
>  [4]: https://lists.alioth.debian.org/pipermail/sane-devel/2018-
> January/035898.html
>  [5]: https://lists.alioth.debian.org/pipermail/sane-devel/2018-
> January/035899.html
>  [6]: https://lists.alioth.debian.org/pipermail/sane-devel/2018-
> January/035921.html
>  [7]: https://lists.alioth.debian.org/pipermail/sane-devel/2018-
> January/035912.html
>
> Taking this all in, and putting the mailing lists issue aside for a bit,
> I still prefer moving to GitLab.com.  In terms of repository, issues and
> merge/pull request support it offers pretty much the same as GitHub, but
> on top of that allows you to log in using accounts users may have with
> (selected) other services.  This, I think, lowers the barrier to report
> issues.  Furthermore, GitLab.com comes with CI out-of-the-box (which is
> used already by the current *unofficial* mirror, btw!).
>
> The idea of putting a repository mirror on GitHub is interesting but I'm
> not sure how pull requests and issues would work out if things are split
> over multiple sites.
>
> Back to mailing lists, I think that for the short term making use of the
> Alioth mail continuation project[8] is our best alternative, although I
> am not exactly clear on that project's status.  If I understand things
> correctly the current list maintainer will be asked to opt in before
> Alioth is discontinued.
>
> I have also considered moving to lists.debian.org but in that case we
> probably won't be able to make the list subscriber-only or moderate
> incoming posts[9][10].
>
>  [8]: https://wiki.debian.org/Alioth/MailingListContinuation
>  [9]: https://wiki.debian.org/Alioth#Mailing_lists
>  [10]: https://www.debian.org/MailingLists/HOWTO_start_list
>
> In either case, sane-commit is extremely likely to disappear (you can
> use the commit notification functionality of GitLab instead).  As for
> sane-standard (which has seen less than 100KB gzipped traffic since July
> 2004!), I think it doesn't serve any purpose.  SANE standard discussions
> can be held on sane-devel.  The sane-announce list sees even less
> traffic but does serve a well-defined purpose (prevent announcements
> from "drowning" in the other traffic) and should be migrated together
> with sane-devel.
>
> Anyway, I'll check the status on [8] and look at some other mailing list
> hosting solutions but 

Re: [sane-devel] PIXMA backend Canon i-SENSYS MF633cdw Support

[Rolf Bensch]

Hi Wojciech,

Please check the version of SANE you are using:
$ scanimage -V

How did you connect your scanner? For testing it should connected on an
USB port.

A remark to your installation: Please remove your self compiled SANE
from your system and follow the install description from the file
INSTALL.linux, which comes with the sources.

Hope this helps.

Cheers,
Rolf


Am 23.01.2018 um 12:46 schrieb Wojciech Teichert:
> pixma.log have one line: scanimage: no SANE devices found
>
> 2018-01-22 19:34 GMT+01:00 Rolf Bensch  >:
>
> Hi Wojciech,
>
> Please provide a logfile created with:
>
> $ SANE_DEBUG_PIXMA=4 scanimage 2> pixma.log > pixma.pnm
>
> Please zip, tar.gz or 7zip pixma.log and send it to me.
>
> Cheers,
> Rolf
>
>
> Am 22.01.2018 um 03:29 schrieb Wojciech Teichert:
>>  scanimage -L
>>
>> No scanners were identified. If you were expecting something
>> different,
>> check that the scanner is plugged in, turned on and detected by the
>> sane-find-scanner tool (if appropriate). Please read the
>> documentation
>> which came with this software (README, FAQ, manpages).
>> root@### sane-find-scanner
>>
>>   # sane-find-scanner will now attempt to detect your scanner. If the
>>   # result is different from what you expected, first make sure your
>>   # scanner is powered up and properly connected to your computer.
>>
>>   # No SCSI scanners found. If you expected something different,
>> make sure that
>>   # you have loaded a kernel SCSI driver for your SCSI adapter.
>>
>> found USB scanner (vendor=0x04a9 [Canon], product=0x27e1
>> [MF633C/635C]) at libusb:001:005
>>   # Your USB scanner was (probably) detected. It may or may not
>> be supported by
>>   # SANE. Try scanimage -L and read the backend's manpage.
>>
>>   # Not checking for parallel port scanners.
>>
>>   # Most Scanners connected to the parallel port or other
>> proprietary ports
>>   # can't be detected by this program.
>> root@### scanimage -L
>>
>> No scanners were identified. If you were expecting something
>> different,
>> check that the scanner is plugged in, turned on and detected by the
>> sane-find-scanner tool (if appropriate). Please read the
>> documentation
>> which came with this software (README, FAQ, manpages)
>>
>> This is new version
>> from git://git.debian.org/sane/sane-backends.git
>>  using ./configure
>> --prefix=/usr --libdir=/usr/lib/x86_64-linux-gnu
>> --sysconfdir=/etc --localstatedir=/var --enable-avahi && make -j4
>>
>> 2018-01-03 21:09 GMT+01:00 Rolf Bensch > >:
>>
>> Hi Wojtek,
>>
>> I just added your scanner to SANE. Please check out the
>> recent version
>> from git or you can use the daily git snapshot tomorrow.
>>
>> Please report if all scanning features (75-600dpi, simple and
>> duplex
>> document feeder) are running with USB. After this you can try
>> the bjnp
>> interface.
>>
>> Hope this helps.
>>
>> Cheers,
>> Rolf
>>
>>
>> Am 13.12.2017 um 09:58 schrieb Wojtek Teichert:
>> >  Can you add support for Canon i-SENSYS MF633cdw scanner?
>>
>>
>
>

-- 
sane-devel mailing list: sane-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
Unsubscribe: Send mail with subject "unsubscribe your_password"
 to sane-devel-requ...@lists.alioth.debian.org

Re: [sane-devel] [janitorial] Relocating the SANE Project

[Markus Heiser]

> Am 26.01.2018 um 09:59 schrieb Olaf Meeuwissen :
> 
> Dear all,
> 
> TL;DR :: Let's move to GitLab.com!  Mailing list TBD.

[ ... ]

> Taking this all in, and putting the mailing lists issue aside for a bit,
> I still prefer moving to GitLab.com.  In terms of repository, issues and
> merge/pull request support it offers pretty much the same as GitHub, but
> on top of that allows you to log in using accounts users may have with
> (selected) other services.  This, I think, lowers the barrier to report
> issues.  Furthermore, GitLab.com comes with CI out-of-the-box (which is
> used already by the current *unofficial* mirror, btw!).
> 
> The idea of putting a repository mirror on GitHub is interesting but I'm
> not sure how pull requests and issues would work out if things are split
> over multiple sites.

Its not a show stopper: pull request can be handled by git itself,
adding the github remote repo and pull the feature branch from there
into the gitlab origin. Vice versa the github users are be able to
fork from gitlab origin this way. 

 What I mean: there is no need for a github mirror. 

Stay with a Single-Point-of-Definition and do not mirror, it will
only confuse the github users.

-- Markus --



-- 
sane-devel mailing list: sane-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
Unsubscribe: Send mail with subject "unsubscribe your_password"
 to sane-devel-requ...@lists.alioth.debian.org

[sane-devel] gscan2pdf v1.8.11 released

[Jeff]

gscan2pdf - A GUI to produce a multipage PDF or DjVu from a scan.

http://gscan2pdf.sourceforge.net/

Five clicks are required to scan several pages and then save all or
a selection as a PDF or DjVu file, including metadata if required.

gscan2pdf can control regular or sheet-fed (ADF) scanners with SANE via
libimage-sane-perl, scanimage or scanadf, and can scan multiple pages at
once. It presents a thumbnail view of scanned pages, and permits simple
operations such as cropping, rotating and deleting pages.

OCR can be used to recognise text in the scans, and the output
embedded in the PDF or DjVu.

PDF conversion is done by PDF::API2.

The resulting document may be saved as a PDF, DjVu, multipage TIFF file,
or single page image file.

Changelog for 1.8.11:
* + preference "Force new scan job between pages"
* support applying profiles resulting in multiple reloads, to prevent
  profile dropdown from being cleared after setting profile.
  Closes #276 (Scan profile stays blank)
* Update to Czech translation (thanks to Pavel Borecki)



signature.asc
Description: OpenPGP digital signature
-- 
sane-devel mailing list: sane-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
Unsubscribe: Send mail with subject "unsubscribe your_password"
 to sane-devel-requ...@lists.alioth.debian.org