Bug#534746: Downgrade fixes

Chris Chiappa wrote: Hi Chris, >> Have you tried a build of the epson2 backend from the HEAD? If that >> doesn't work either, I'll forward the report to the epson2 maintainer. > > Hrmm, I assume if I do a fresh git clone that gets me HEAD? (I have Yes, HEAD of the master branch. > no previous

Bug#534746: Downgrade fixes

On Mon, Dec 28, 2009 at 06:30:44PM +0100, Julien BLACHE wrote: > Have you tried a build of the epson2 backend from the HEAD? If that > doesn't work either, I'll forward the report to the epson2 maintainer. Hrmm, I assume if I do a fresh git clone that gets me HEAD? (I have no previous git experie

Bug#534746: Downgrade fixes

Chris Chiappa wrote: Hi Chris, > I just confirmed what I thought I saw - in 1.0.20-11 the epson2 driver > sees my Epson Stylus Photo RX500 and doesn't work. In 1.0.19-23, it > is seen by the epson driver and does work. In those revisions where > both drivers see it, the epson driver works but

Bug#534746: Downgrade fixes

I just confirmed what I thought I saw - in 1.0.20-11 the epson2 driver sees my Epson Stylus Photo RX500 and doesn't work. In 1.0.19-23, it is seen by the epson driver and does work. In those revisions where both drivers see it, the epson driver works but epson2 doesn't. On Sat, Dec 26, 2009 at 0

Bug#534746: Downgrade fixes

It seems like with this change, my scanner is reported by both the epson and epson2 backends: $ git bisect bad 9227e7d6bc69bddeedd4d66ea55d6ccb41bccff3 is the first bad commit commit 9227e7d6bc69bddeedd4d66ea55d6ccb41bccff3 Author: Alessandro Zummo Date: Tue Nov 18 20:26:55 2008 + fixe

Bug#534746: Downgrade fixes

Chris Chiappa wrote: Hi, > Huh. During bisection, it looks like some snapshots see my scanner > with the 'epson' driver and some with both the 'epson' and 'epson2' > driver. So far, 'epson' has always worked but 'epson2' has always > failed. I'm guessing (unconfirmed) that the old release onl

Bug#534746: Downgrade fixes

Huh. During bisection, it looks like some snapshots see my scanner with the 'epson' driver and some with both the 'epson' and 'epson2' driver. So far, 'epson' has always worked but 'epson2' has always failed. I'm guessing (unconfirmed) that the old release only detects under 'epson' and the new

Bug#534746: Downgrade fixes

Chris Chiappa wrote: Hi, >> So this is definitely a bug in the epson2 backend. Can you try to bisect >> it? > I might be able to find some time this weekend - is there a Debian > repository with all of the intervening versions somewhere? > Alternatively, do you have a pointer offhand about doing

Bug#534746: Downgrade fixes

On Thu, Dec 24, 2009 at 05:38:16PM +0100, Julien BLACHE wrote: > > Downgrading libsane to 1.0.20-9 did not fix it, but downgrading to > > 1.0.19-23 did. > > So this is definitely a bug in the epson2 backend. Can you try to bisect > it? I might be able to find some time this weekend - is there a De

Bug#534746: Downgrade fixes

Chris Chiappa wrote: Hi, > Downgrading libsane to 1.0.20-9 did not fix it, but downgrading to > 1.0.19-23 did. So this is definitely a bug in the epson2 backend. Can you try to bisect it? JB. -- Julien BLACHE - Debian & GNU/Linux Developer - Public key available on

Bug#534746: Downgrade fixes

Downgrading libsane to 1.0.20-9 did not fix it, but downgrading to 1.0.19-23 did. -- ..ooOO ch...@chiappa.net | My opinions are my own OOoo.. ..ooOO chris.chia...@oracle.com | and certainly not those OOoo.. ..ooOO http://www.chiappa.net/~chris/ | of my employer OOoo.