Bug#816857: gimagereader: fails to launch with "symbol lookup error"

Hi all, just to keep you informed: The ABI breakage is fixed upstream now: https://github.com/tesseract-ocr/tesseract/commit/7461b617433757105db08b3bb4fca47eee3c96d7 Best, Philip signature.asc Description: PGP signature

Bug#816857: gimagereader: fails to launch with "symbol lookup error"

IRC people tell me that a transition bug will fix everything. There is an existing transition bug #815919.

Bug#816857: gimagereader: fails to launch with "symbol lookup error"

Hi Jeff, > Jeff Breidenbach hat am 7. März 2016 um 21:22 > geschrieben: > Thanks for working with me and sorry about the trouble. Don't worry, things like that happen - let's just try to solve the bug completely now :) > I don't know what you mean by not closing bug #815056 >

Bug#816857: gimagereader: fails to launch with "symbol lookup error"

jbreiden: Just report a transition bug for release.debian.org to +transition back So they rebuild the stuff against the old ABI again

Bug#816857: gimagereader: fails to launch with "symbol lookup error"

Thanks for working with me and sorry about the trouble. I don't know what you mean by not closing bug #815056 properly. The bug tracker says it is closed. https://bugs.debian.org/cgi-bin/pkgreport.cgi?repeatmerged=no=tesseract If I look at the package tracking system, it seems to be claiming

Bug#816857: gimagereader: fails to launch with "symbol lookup error"

It must be mad that there is no libtesseract4 anymore. I'm going to try to get help for that on IRC.

Bug#816857: gimagereader: fails to launch with "symbol lookup error"

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

Bug#816857: gimagereader: fails to launch with "symbol lookup error"

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.

Bug#816857: gimagereader: fails to launch with "symbol lookup error"

Hi Jeff and Jeffrey, I think tessaract broke it's ABI again without taking care of renaiming the package name and bumping SONAME :( That's really annoying as gimagereader broke again. (See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794489 for reference) Building with tessaract from

Bug#816857: gimagereader: fails to launch with "symbol lookup error"

Package: gimagereader Version: 3.1.2+git368fa8f-2 Severity: grave Justification: renders package unusable Dear Maintainer, This is the complete error messager: gimagereader-gtk: symbol lookup error: gimagereader-gtk: undefined symbol: _ZN9tesseract11TessBaseAPI13AnalyseLayoutEv