Bug#815056: libtesseract4: fails to upgrade from libtesseract3

2016-02-24 Thread Jeff Breidenbach
> There was an accidental ABI breakage a while ago > And I thought that bumping to libtesseract4 was the right thing to do ... The important question is: How did this ABI break happen? Upstream change or only an effect of the C++ transition? > I had been assuming upstream change > But actually

Bug#815056: libtesseract4: fails to upgrade from libtesseract3

2016-02-24 Thread Jeff Breidenbach
Why? I was asked strongly by a Debian Developer in 794489 to bump the libtesseract version. I suspect 742027 was related. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794489 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=742027 I historically have a lot of trouble with transitions, and

Bug#815056: libtesseract4: fails to upgrade from libtesseract3

2016-02-18 Thread Michael Biebl
On Thu, 18 Feb 2016 11:09:04 +0100 IOhannes m zmoelnig wrote: > Package: libtesseract4 > Version: 3.04.01-1 > Severity: serious > Justification: Policy 7.4 > > Dear Maintainer, > > libtesseract4 provides at least one identical file as libtesseract3 without > declaring a

Bug#815056: libtesseract4: fails to upgrade from libtesseract3

2016-02-18 Thread IOhannes m zmoelnig
Package: libtesseract4 Version: 3.04.01-1 Severity: serious Justification: Policy 7.4 Dear Maintainer, libtesseract4 provides at least one identical file as libtesseract3 without declaring a "Conflicts" relationshipt, does breaking any upgrade: > Preparing to unpack