Hi, WRT Aurelien's message and the IRC log, a minor correction to your conversation: my package depends on (libtiff5-dev | libtiff4-dev), not (libtiff5-dev | libtiff-dev). libtiff-dev is *only* provided by libtiff4-dev [1], libtiff4 is in oldlibs [2] as I said -- that's why I wanted to "upgrade" to v5. There are ongoing (or recently finished) transitions with libpng and others, so I figured that this was another imminent one before the freeze.
[1] $ aptitude show libtiff-dev No current or candidate version found for libtiff-dev Package: libtiff-dev State: not a real package Provided by: libtiff4-dev [2] $ apt-cache show libtiff4 | grep Section Section: oldlibs (Note: I only import from a single mirror and unstable, no funky stuff mixing repositories or apt-pinning). 2012/6/9 Julien Cristau <jcris...@debian.org>: > Buildds ignore | in build-dependencies. Please use the unversioned > libtiff-dev, it'll point to the right version. Using libtiff5-dev in > wheezy is discouraged, we want everything to move to symbol-versioned > libtiff4 first. Should I also do this for other packages that I "converted" to v5? They don't seem to have trouble using v5. > libtiff4 being in oldlibs sounds like a bug to me. Who should point that to the maintainer? The release team? If I'm not mistaken, you're part of that team (Julien). Cheers. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
