I've found that the new version of 'file' (4.25-1, i686) recognizes png files as data. The previous version (4.24-1) is ok. This is an upstream bug (reproduced building the package in a five year old suse system) related to the changes in the magic file. I've not digged in the code of the program so I don't know how/where the problem arises. I fixed the bug patching the source file magic/Magdir/images (see attachment) and rebuilding magic.mgc. Please, someone let me know if this is the right place for this kind of messages or if I should open a new task on Flyspray.
--- magic/Magdir/images.orig 2008-07-02 17:16:52.000000000 +0200 +++ magic/Magdir/images 2008-07-16 22:00:15.000000000 +0200 @@ -75,19 +75,19 @@ # # 137 P N G \r \n ^Z \n [4-byte length] H E A D [HEAD data] [HEAD crc] ... # -0 string \x89PNG\x0d\x0a\x1a\x0a PNG image +0 bequad 0x89504e470d0a1a0a PNG image !:mime image/png ->>16 belong x \b, %ld x ->>20 belong x %ld, ->>24 byte x %d-bit ->>25 byte 0 grayscale, ->>25 byte 2 \b/color RGB, ->>25 byte 3 colormap, ->>25 byte 4 gray+alpha, ->>25 byte 6 \b/color RGBA, -#>>26 byte 0 deflate/32K, ->>28 byte 0 non-interlaced ->>28 byte 1 interlaced +>16 belong x \b, %ld x +>20 belong x %ld, +>24 byte x %d-bit +>25 byte 0 grayscale, +>25 byte 2 \b/color RGB, +>25 byte 3 colormap, +>25 byte 4 gray+alpha, +>25 byte 6 \b/color RGBA, +#>26 byte 0 deflate/32K, +>28 byte 0 non-interlaced +>28 byte 1 interlaced # possible GIF replacements; none yet released! # (Greg Roelofs, newt@xxxxxxxxxxxx)
