public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Lemures Lemniscati <lemures.lemniscati@gmail.com>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] Updated: ImageMagick-6.9.9.11-1
Date: Sun, 09 Sep 2018 09:48:00 -0000	[thread overview]
Message-ID: <20180909184848.09A6.50F79699@gmail.com> (raw)
In-Reply-To: <20180908224014.1AC4.50F79699@gmail.com>

Thank you for maintainers.
I apologize for bothering you.

Reporting about cases:
  ImageMagick 6.9.9-11 has an issue,
  ImageMagick 6.9.10-11 resolves it,
  ImageMagick 7.0.8-11 resolves it,
and hoping the current package ImageMagick-6.9.9.11-3 will be updated.

Tested by building from the sources as follows
(because I don't know about cygport and want to test only 'identify'):

  ./configure --without-wmf
  make


Results are:
-----------------
Version 6.9.9-11:
  Built from the source ImageMagick-6.9.9-11.tar.lz
  in ImageMagick-6.9.9.11-3-src.tar.xz

  It hangs:
    identify -verbose a_depth1.psd
  while it works fine:
    identify a_depth1.psd


-----------------
Version 6.9.10-11:
  Built from the source
  https://www.imagemagick.org/download/releases/ImageMagick-6.9.10-11.tar.xz

  Both of them work fine:
    identify -verbose a_depth1.psd
    identify a_depth1.psd


-----------------
Version 7.0.8-11:
  Built from the source
  https://www.imagemagick.org/download/releases/ImageMagick-7.0.8-11.tar.xz

  Both of them work fine:
    identify -verbose a_depth1.psd
    identify a_depth1.psd


And this is the data file.
=== a_depth1.psd ===

base -d << END > a_depth1.psd
OEJQUwABAAAAAAAAAAEAAAAbAAAAJQABAAAAAAAAAAAAHDhCSU0D7QAAAAAAEAAAAAEAAQABAAAA
AQABAAEAAACoAAAAoAABAAAAAAAAAAAAAAAbAAAAJQABAAAAAABqOEJJTW5vcm3/AAEAAAAADAAA
AAAAAAAAAkwxAAACeJxjYGBgYGcAEfb///9/bv+/HUQwA4l/cOIX08/n1v8Z/wG5zf/T7f9X/39u
e76ed7nO//8/n+vUf//xHMRabn+8/Oxy+//1IG3s/9Ot/wB12P1irkU2Cmzy/34QAbSNAW45ADXc
TDUAAAAAAAEABQAFAAcACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgA
BwAFAAX9AAAHgP0AAAeAAD/+/wDngAE//wKH/+eAAT//AgP/54ABP/4CA//ngAE//gID/+eAAT/6
AgL554ABO/8CAf7ngAE//gKD/2eAAT//Anv/54ABPc8Cfw2ngAEs/wL/+eeAASx/Avf454ABLP8C
//mngAE/xwJ3zaeAAT//An//54ABP/4CB/9ngAE7/AIB/ueAAT76AgN954ABP/4CA//ngAE//gID
/+eAAT//AgP/54ABP/8Cj//ngAA//v8A54D9AAAHgP0AAAeA
END

Regards,

--
Lemures Lemniscati


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

  reply	other threads:[~2018-09-09  9:48 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-06 16:45 Marco Atzeri
2018-09-08 11:10 ` Lemures Lemniscati
2018-09-08 11:59   ` Marco Atzeri
     [not found]     ` <20180908211400.1280.50F79699@gmail.com>
2018-09-08 13:10       ` Marco Atzeri
2018-09-08 13:40         ` Lemures Lemniscati
2018-09-09  9:48           ` Lemures Lemniscati [this message]
2018-09-09 16:05             ` Marco Atzeri
2018-09-10 14:23               ` Lemures Lemniscati
2018-09-10 14:55                 ` Marco Atzeri

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180909184848.09A6.50F79699@gmail.com \
    --to=lemures.lemniscati@gmail.com \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).