AWARE SYSTEMS
TIFF and LibTiff Mail List Archive

Thread

2009.08.28 01:32 "[Tiff] tiff 3.9.0 writes bad files", by Bob Friesenhahn
2009.08.28 02:09 "Re: [Tiff] tiff 3.9.0 writes bad files", by Bob Friesenhahn
2009.08.28 03:13 "Re: [Tiff] tiff 3.9.0 writes bad files", by Bob Friesenhahn
2009.08.30 07:09 "Re: [Tiff] tiff 3.9.0 writes bad files", by Andreas Kleinert
2009.08.28 03:23 "Re: [Tiff] tiff 3.9.0 writes bad files", by Bob Friesenhahn
2009.08.28 04:11 "Re: [Tiff] tiff 3.9.0 writes bad files", by Lee Howard
2009.08.28 04:22 "Re: [Tiff] tiff 3.9.0 writes bad files", by Bob Friesenhahn
2009.08.30 16:06 "Re: [Tiff] tiff 3.9.0 writes bad files", by Bob Friesenhahn

2009.08.28 04:11 "Re: [Tiff] tiff 3.9.0 writes bad files", by Lee Howard

Is no one else seeing this problem? Libtiff 3.9.0 was released on the 20th.

I've been distributing a copy of libtiff 3.9.0beta1 intended for HylaFAX users since November 2007 without any reports about its brokenness. Sourceforge reports 118 downloads of it. I can't speak to how many actually are in-use. But that was a long time ago, so I don't recall exactly the amount of testing that I did with it, but I know that I did enough for me to feel comfortable with 3.9.0 functionality with HylaFAX.

(I tend to use 3.8.2, however, as that's often what comes with the distro.)

I know that's not a very concrete set of evidence, but I would suggest that it presents a likelihood that whatever problem there was in the 3.9.0 release, it entered the source code *after* beta1.

For what it's worth, generally it's a good idea to run a beta and a release candidacy period... even after applying what otherwise would seem to be trivial or well-exposed patches. It saves time in the long-run from botching releases. I don't fault anyone in this, however, as I've had my own mistakes in this regard multiple times.

Thanks,

Lee.