[MacPorts] #20618: ImageMagick: Strange symptom: non-error error

[MacPorts]

#20618: ImageMagick: Strange symptom: non-error error
---------------------------------------+------------------------------------
 Reporter:  objectivecanine@…          |       Owner:  ryandesign@…           
     Type:  defect                     |      Status:  new                    
 Priority:  Normal                     |   Milestone:                         
Component:  ports                      |     Version:  1.7.1                  
 Keywords:  color profile              |        Port:  ImageMagick            
---------------------------------------+------------------------------------
Changes (by blb@…):

  * keywords:  ImageMagick, color profile => color profile
  * owner:  macports-tickets@… => ryandesign@…
  * port:  => ImageMagick


Old description:

> Running ImageMagick via MacPorts on a Mac Pro, I've discovered a bizarre
> symptom. I don't see the same issue on other ImageMagick builds on other
> systems here, even oame-version builds.
>
> tiger:~ keanu$ convert -monitor Scans/Input/scan-00000349.tif -profile
> Metadata/Profiles/Epson\ V500.icc -intent perceptual -profile
> Metadata/Profiles/ColorMatch\ RGB.icc test.tif
> Load/Image//Volumes/rottweiler/Scans/Input: 100%  [scan-00000349.tif]
> Save image: 100%  [test.tif]
> convert: unable to get registry ID
> `cache:/Volumes/rottweiler/Metadata/Profiles/ColorMatch RGB.icc' @
> registry.c/GetImageRegistry/224.
>
> tiger:~ keanu$ identify -ping test.tif
> test.tif TIFF 13600x17760 13600x17760+0+0 16-bit DirectClass 1.3498gb
>
> Despite the error message (and the nonzero exit status), the file was
> created successfully, contains the correct profile, everything's fine...
>
> However, to say the nonzero exit is confusing every script I've written
> that checks for errors is an understatement.
>
> Given that I don't get this problem on a Debian Linux system (with the
> same ImageMagick version, rather than the prepackaged but woefully old
> Debian-shipped version) I suspect this may not be an upstream bug and am
> reporting it here.

New description:

 Running ImageMagick via MacPorts on a Mac Pro, I've discovered a bizarre
 symptom. I don't see the same issue on other ImageMagick builds on other
 systems here, even oame-version builds.
 {{{
 tiger:~ keanu$ convert -monitor Scans/Input/scan-00000349.tif -profile
 Metadata/Profiles/Epson\ V500.icc -intent perceptual -profile
 Metadata/Profiles/ColorMatch\ RGB.icc test.tif
 Load/Image//Volumes/rottweiler/Scans/Input: 100%  [scan-00000349.tif]
 Save image: 100%  [test.tif]
 convert: unable to get registry ID
 `cache:/Volumes/rottweiler/Metadata/Profiles/ColorMatch RGB.icc' @
 registry.c/GetImageRegistry/224.

 tiger:~ keanu$ identify -ping test.tif
 test.tif TIFF 13600x17760 13600x17760+0+0 16-bit DirectClass 1.3498gb
 }}}
 Despite the error message (and the nonzero exit status), the file was
 created successfully, contains the correct profile, everything's fine...

 However, to say the nonzero exit is confusing every script I've written
 that checks for errors is an understatement.

 Given that I don't get this problem on a Debian Linux system (with the
 same ImageMagick version, rather than the prepackaged but woefully old
 Debian-shipped version) I suspect this may not be an upstream bug and am
 reporting it here.

--

Comment:

 Did you build ImageMagick with +lcms variant, perhaps that would help?

-- 
Ticket URL: <http://trac.macports.org/ticket/20618#comment:1>
MacPorts <http://www.macports.org/>
Ports system for Mac OS