Hi Jeff, thanks for your effort! I think the problem right now is that 3.04.01-4 is still not in testing (I think you didn't close bug #815056 properly). So making tesseract transition to testing would make the situation much better. It might be, that I still have to rebuild gimagereader, as it was build against -3, but let's deal with that later. Please just make sure that tesseract -4 enters testing soon. (And please help to convince upstream to move the function to baseapi.cpp again).
Best, Philip > Jeff Breidenbach <j...@jab.org> hat am 7. März 2016 um 20:56 > geschrieben: > > > I'm in over my head, so I asked for help. The folks on debian-devel > IRC channel advised me to not bump soname and instead attempt > an ABI repair. It was supposed to be harmless to gimagereader. > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815056 > > I'm really not sure what to do at this point. The Debian package > is doing exactly what you asked for, unless I made a mistake. > > https://github.com/tesseract-ocr/tesseract/issues/254
