Package: *cuneiform*
Version: *1.1.0+dfsg-7*
Severity: important
Tags: patch

Compile fails with 
CF_DATADIR=/<<BUILDDIR>>/cuneiform-1.1.0+dfsg/datafiles/ 
debian/tests/ground-truth obj/cuneiform
images/phototest.tif ... FAIL
--- images/phototest.tif.txt    2011-04-19 12:49:57.000000000 +0000
+++ /tmp/cuneiform.test.KgXcP8dD/phototest.tif.out      2018-01-14 
03:21:46.536688277 +0000
@@ -1,7 +1,7 @@
-This is a lot of 12 point text to test the 
-ocr code and see if it works on all types 
+This is a lot of 12 poiet text to test the 
+ocr code aed see if it works oe all types 
 of file format. 
-The quick brown dog jumped over the 
+The quick browe dog jumped over the 
 lazy fox. The quick brown dog jumped 
 over the lazy fox. The quick brown dog 
 jumped over the lazy fox. The quick 
debian/rules:58: recipe for target 'obj/test-stamp' failed
make: *** [obj/test-stamp] Error 1
dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit 
status 2

/*This sounds a similar problem reported for armel on ubuntu
https://bugs.launchpad.net/ubuntu/+source/cuneiform/+bug/791305
*/

/**/

    This bug was fixed in the package cuneiform - 1.1.0+dfsg-6

    ---------------
    cuneiform (1.1.0+dfsg-6) unstable; urgency=medium

      [ Andreas Beckmann ]
      * QA upload.
      * Incorporate changes from Ubuntu.
      * gcc-6.patch: New, fix more FTBFS issues with GCC 6.
      * typos.patch: New, fix typos.

      [ Bhavani Shankar ]
      * Fix double FTBFS with unsigned char and GCC 6. (LP: #791305
    <https://bugs.launchpad.net/bugs/791305>)
        (Closes: #787207, #837360)
      * Incorporate patch to fix buffer overflow during crash. Thanks
        Sławomir Nizio. Hopefully fix (LP: #978183
    <https://bugs.launchpad.net/bugs/978183>), (LP: #593409
    <https://bugs.launchpad.net/bugs/593409>), (LP: #791864
    <https://bugs.launchpad.net/bugs/791864>),
        (LP: #996309 <https://bugs.launchpad.net/bugs/996309>). (Closes:
    #781354)

     -- Andreas Beckmann <email address hidden> Sun, 23 Apr 2017
    14:02:07 +0200


Reply via email to