I'm not sure where the tiff transition falls on your long list, but I thought I'd add a little more information on what issues we may encounter.
Jay Berkenbilt <q...@debian.org> wrote: > Wasting no time, I'd like to remind the release team that I'm really > hoping Jessie will ship with only one version of the tiff library: > . . . > > The vast majority of packages that use tiff 3.x will transition to tiff > 4.x with no changes to their code. Those packages that already build > depend on libtiff-dev instead of libtiff4-dev may even get away with > just a binary NMU. There are some packages that may require small code > changes to take care of places where APIs have changed to support > bigtiff. . . . Following up on this, I'm include the following remark from Tom Lane, the person at Red Hat who manages the tiff package and who is active on the upstream mailing list (and who I have talked to many times about coordinating security issues, etc.): > > libtiff4 is source-compatible but not binary-compatible with libtiff3. > > The breaks were necessary to support large files. > > FWIW, my experience with updating the Fedora distro is that 4.0 is only > about 99.9% source-compatible either. There were a few packages that > required source-code fixes (freeimage, tkimg, xloadimage according to > my notes). As an example, the library no longer exposes the contents > of struct TIFFFieldInfo. In any case, as Fedora has already made progress in this area, I can mine their patches for any required NMUs. -- Jay Berkenbilt <q...@debian.org> -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130514110904.0207178878.qww314...@jberkenbilt-linux.appiancorp.com
