[Bug 221391] graphics/zbar can work with ImageMagick-7 just as well
bugzilla-noreply at freebsd.org
bugzilla-noreply at freebsd.org
Fri Sep 15 14:08:26 UTC 2017
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221391
Oliver Heesakkers <dev2 at heesakkers.info> changed:
What |Removed |Added
----------------------------------------------------------------------------
Flags|maintainer-feedback?(dev2 at h |maintainer-feedback-
|eesakkers.info) |
--- Comment #2 from Oliver Heesakkers <dev2 at heesakkers.info> ---
I've stumbled upon a problem with this.
Using the samen command on a couple of example pics, I get
######################################
# with ImageMagick6 and current zbar #
######################################
EAN-8.jpg: EAN-8:50184385
UPC-A.png: EAN-13:0036000291452
barcode.png: EAN-13:9876543210128
code128.png: CODE-128:010123456789012815051231
code39.png: CODE-39:123ABC
ean-13.jpg: EAN-13:7612345000121
interleaved2of5.png: I2/5:12345678
upc-e.gif: EAN-13:0012345000065
########################################
# with ImageMagick6 and proposed patch #
########################################
EAN-8.jpg: ERROR: unable to open image `EAN-8.jpg': No such file or directory @
error/blob.c/OpenBlob/2701
UPC-A.png: ERROR: unable to open image `UPC-A.png': No such file or directory @
error/blob.c/OpenBlob/2701
barcode.png: ERROR: unable to open image `barcode.png': No such file or
directory @ error/blob.c/OpenBlob/2701
code128.png: ERROR: unable to open image `code128.png': No such file or
directory @ error/blob.c/OpenBlob/2701
code39.png: ERROR: unable to open image `code39.png': No such file or directory
@ error/blob.c/OpenBlob/2701
ean-13.jpg: ERROR: unable to open image `ean-13.jpg': No such file or directory
@ error/blob.c/OpenBlob/2701
interleaved2of5.png: ERROR: unable to open image `interleaved2of5.png': No such
file or directory @ error/blob.c/OpenBlob/2701
upc-e.gif: ERROR: unable to open image `upc-e.gif': No such file or directory @
error/blob.c/OpenBlob/2701
I have yet to try ImageMagick7 and the proposed patch, but at present I would
advise against committing these changes.
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the freebsd-ports-bugs
mailing list