You are not logged in.
After upgrading imagemagick (6.6.1.5-1 -> 6.6.4.10-1), I have this:
> file image.jpg
image.jpg: JPEG image data, JFIF standard 1.01
> convert image.jpg image.ps
> file image.ps
image.ps: JPEG image data, JFIF standard 1.01Expected output is, of course, "image.ps: PostScript document text ..."; that's what 6.6.1.5 used to produce just before the upgrade. The output file isn't a simple copy of image.png, but it's the same as the result of "convert image.jpg image.1.jpg". Converting between jpg and png works as expected.
It's not the first issue of this kind, some time ago it lost xwd support in a similar way. I guess it was during 6.5.8.5-1 -> 6.6.1.5-1 upgrade, but I wasn't bothered enough to check it.
Does anyone know how to make it work again? Is it some kind of call order change I'm missing, or is it a real bug/misconfiguration? I'll going to do some research myself now, but any ideas will be appreciated.
Offline
Ugh, ok, solved.
PS filter apparently depends on ghostscript >= 9. I had 8.71, and pacman neither complained nor tried to upgrade gs. PKGBULD lists "ghostscript>=9.0" in $makedepends, not in $depends.
Colon characters within filename seem to confuse imagemagick even if whatever preceedes them doesn't look like a format name at all. My xwd commands looked like "xwd ... | convert - xwd-2010.12.20-14:31:44.png", now it's "... convert - png:xwd-2010.12.20-14:31:44.png" and everything works well.
Offline