On Wednesday, 3 January 2018 3:54 AM, Dider 'OdyX' Raboud 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. > >Why has this changed?
I don't know. This may be indirectly caused by fixing #780807. > From the tiff changelog in version 4.0.3-10: | Packages that still declare build dependencies on libtiff4-dev must now | build depend on libtiff-dev instead, or if a versioned dependency is | required, libtiff5-dev with a specific version. >From the libtiff-dev description: | This package should be used in Build-Depends to ease transitions. >> Please depend on libtiff5-dev to re-enable multi-arch support. >This seems like something in need to be fixed in src:tiff on the libtiff-dev >binary package, isn't it? Potentially, yes. But libtiff-dev is part of the oldlibs section and is described as a transitional package. Plus it has been made (implicitly) Multi-Arch: no. Of course, this can be fixed. > 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. Yes, cups may need to Build-Depend on libtiff5-dev, but this does reverse the change from a few years ago.
