Control: tags -1 +pending Hi,
On Tue, Jan 2, 2018 at 5:54 PM, Didier 'OdyX' Raboud <[email protected]> wrote: > Le vendredi, 22 décembre 2017, 12.02:25 h CET Hugh McMaster a écrit : >> The package libtiff-dev is now a transitional package >> and is no longer marked Multi-Arch: same. Transitional now means it will be the -dev package for tiff. > Why has this changed? It was a virtual package and libtiff5-dev provided it. Now it's a real, basically empty package that pulls in the libtiff5-dev package. > From the libtiff-dev description: >> This package should be used in Build-Depends to ease transitions. Indeed, all packages that build depend on libtiff5-dev should change to this one. > Le vendredi, 22 décembre 2017, 12.02:25 h CET Hugh McMaster a écrit : >> Please depend on libtiff5-dev to re-enable multi-arch support. Please Hugh, do not state wrong things like this. What's the point you are trying to solve? > This seems like something in need to be fixed in src:tiff on the libtiff-dev > binary package, isn't it? Yup, while libtiff-dev currently doesn't ship any libraries I'll mark it as multi-arch. > src:tiff maintainers; in order to speed up this bug's handling, I'm > reassigning this to libtiff-dev. I'm happy to discuss if CUPS should be made > to directly Build-Depend on libtiff5-dev instead of libtiff-dev, but this > seems to really defeat the point of a versionless -dev package. There's no need to change anything in CUPS and hopefully you didn't change its multi-arch settings. Regards, Laszlo/GCS
