AWARE SYSTEMS
TIFF and LibTiff Mail List Archive

Thread

2017.03.04 10:59 "[Tiff] started seeing breakage with libtiff", by John
2017.03.04 12:10 "Re: [Tiff] started seeing breakage with libtiff", by Even Rouault
2017.03.04 13:08 "Re: [Tiff] started seeing breakage with libtiff", by John
2017.03.04 18:51 "Re: [Tiff] started seeing breakage with libtiff", by John
2017.03.04 19:19 "Re: [Tiff] started seeing breakage with libtiff", by Bob Friesenhahn
2017.03.04 19:53 "Re: [Tiff] started seeing breakage with libtiff", by Even Rouault
2017.03.05 09:53 "Re: [Tiff] started seeing breakage with libtiff", by John
2017.03.06 15:29 "Re: [Tiff] started seeing breakage with libtiff", by Lee Howard
2017.03.06 15:46 "Re: [Tiff] started seeing breakage with libtiff", by Bob Friesenhahn
2017.03.06 15:59 "Re: [Tiff] started seeing breakage with libtiff", by Toby Thain
2017.03.06 16:26 "Re: [Tiff] started seeing breakage with libtiff", by Lee Howard

2017.03.05 09:53 "Re: [Tiff] started seeing breakage with libtiff", by John

On 4 March 2017 at 19:53, Even Rouault <even.rouault@spatialys.com> wrote:

that in official libtiff is applied in the TIFF_SETGET_C16_ASCII cases (line 5017 in HEAD) and in the TIFF_SETGET_C32_ASCII cases (line 5194 in CVS HEAD) has been wrongly applied in Debian in the TIFF_SETGET_C16_UINT8 case (line 5008) and TIFF_SETGET_C32_UINT8 case (line 5180)...

Thank you Even, I'll fwd your mail to the debian/ubuntu bug page, I hope that's OK.

John