Bug#658478: tesseract: no tesseract-ocr-dev -> libtesseract-dev upgrade path

2012-03-01 Thread Jeff Breidenbach
The dummy transitional package I am uploading right now will still not allow Ocropus to build or run; that awaits a future upstream Ocropus release. The other dependency, Sikuli, has already been ported and should be good to go. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.

Bug#658478: tesseract: no tesseract-ocr-dev -> libtesseract-dev upgrade path

2012-03-01 Thread Jeff Breidenbach
Thank you, Guido. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#658478: tesseract: no tesseract-ocr-dev -> libtesseract-dev upgrade path

2012-02-27 Thread Guido van Steen
>>3) Users who have tesseract-ocr-dev installed will be left with their >>old version on upgrade, unless they install libtesseract-dev manually. > >Correct me if I am wrong, but won't apt-get dist-upgrade also take >care of this? I have a Replaces line in the new package. What else >would you sugge

Bug#658478:

2012-02-06 Thread Jeff Breidenbach
Statement from Sikuli upstream Sikuli has an experimental tesseract 3 branch https://github.com/sikuli/sikuli/tree/feature/tesseract3. The main reason we aren't not switching to tesseract 3 in an official release is that its recognition performance is worse than 2.04 in our dataset. (Not very

Bug#658478: tesseract: no tesseract-ocr-dev -> libtesseract-dev upgrade path

2012-02-06 Thread Jeff Breidenbach
$ grep-dctrl -FSource:Build-Depends -s Package,Build-Depends tesseract-ocr-dev < /var/lib/apt/lists/ftp.us.debian.org_debian_dists_sid_main_source_Sources Package: ocropus Build-Depends: debhelper (>= 7.0.50~), dpkg-dev (>= 1.15.7), autotools-dev, autoconf, automake1.9, libtool, liblua5.1-0-dev, li

Bug#658478: tesseract: no tesseract-ocr-dev -> libtesseract-dev upgrade path

2012-02-03 Thread Jeff Breidenbach
>2) There are packages that build-depend on tesseract-ocr-dev, which you >now left unbuildable. Also, I strongly suspect the build will break anyway; Tesseract 3.0.x is a big jump from 2.0.4. If you are thinking about Ocropus in particular, let me point you to some relevant discussion. http://gro

Bug#658478: tesseract: no tesseract-ocr-dev -> libtesseract-dev upgrade path

2012-02-03 Thread Jeff Breidenbach
>1) There's no mention of this rename in the changelog. Fixed (will upload shortly) >2) There are packages that build-depend on tesseract-ocr-dev, which you >now left unbuildable. What are they? What should I do about this aside from contacting the maintainers? $ apt-rdepends -r -b tesseract-oc

Bug#658478: tesseract: no tesseract-ocr-dev -> libtesseract-dev upgrade path

2012-02-03 Thread Jakub Wilk
Source: tesseract Version: 3.02-1 Severity: important tesseract-ocr-dev has been renamed to libtesseract-dev. This is great, but: 1) There's no mention of this rename in the changelog. 2) There are packages that build-depend on tesseract-ocr-dev, which you now left unbuildable. 3) Users who ha