I guess tiff has been left stale for a while (sorry) with the last two versions (3.7.3 and 3.7.4) left as stable/unstable for several months. The latest stable upstream release is now 3.8.2, and there are some fixes that should be applied (see bug 131602 for the link to the upstream bug). I've propagated the arch's from the previous version (3.7.4) to 3.8.2, and marked stable the ones I have handy (3.7.4 should have been stablized long ago). The new libtiff 3.8.2 ebuild checks out okay so far on my 4 arch's, so I'd like to get it tested and stablized over the next few weeks (possible future bugs permitting). Thanks.
Bump for feedback (only a week to go...)
All tests passed, and cups built fine against it. Stable on the SPARCenstein.
Looks fine on ppc, marked ppc stable.
stable on ppc64
Alpha done wrt bug #129675.
Any chance of getting the remaining arches stablized? The recent security bug is now closed... Thanks.
Sorry to do this (I started this bug before the security issues came up) but we could use another round of arch testing on the new tiff ebuild; it applies several patches, including the new JBIG support from the upstream CVS, so I think it deserves some testing (in fact, the security team may want it stablized sooner). Thanks again...
If it is a security fix, then I would say it should be "due" on June 30th, before my snapshot for 2006.1... ;]
I installed tiff-3.8.2-r1 and recompiled gimp-2.2.8-r1 with tiff USE flag on x86 and I was able to load, edit and save tiff image.
amd64 and x86 done... that's two arches for the price of one... ;]
sparc stable.
tiff-3.8.2-r1 stable on ppc.
All tests pass on alpha for -r1. Was also able to manipulate a tiff image with no problems in gimp as well as convert to postscript (tiff2ps), pdf (tiff2pdf) and convert a bitmap to tiff (bmp2tiff)
alpha stable.
Closing, since we just bumped a security patch last night...