2016-01-23 4:13 GMT+01:00 Jonas Smedegaard <d...@jones.dk>: > Quoting Balint Reczey (2016-01-22 22:29:30) >> On Fri, 22 Jan 2016 10:21:59 +0000 (UTC) Gianfranco Costamagna >> <costamagnagianfra...@yahoo.it> wrote: >> ... >>> - libpng12-dev | libpng-dev, >>> + libpng-dev | libpng12-dev, >> I have already prepared the fix in git and I'm waiting for libpng-dev >> to become a non-virtual package. >> >> From Debian Policy 7.5 Virtual packages - Provides: >> To specify which of a set of real packages should be the default to >> satisfy a particular dependency on a virtual package, list the real >> package as an alternative before the virtual one. > > That section of policy talks about _dependencies_ whereas the change > done above is a _build-dependency_. > > It is a common pattern in Debian to provide a virtual library > development package. Purpose of the section above is to ensure > deterministic install (non-random install) but that is ensured by the > maintainer of the library package only having a single package available > in any suite at a time providing the virtual package. I assumed this section covers build-dependencies to help determinism, in case there happens to be two packages providing the virtual package.
There is a long thread on debian-devel starting here: https://lists.debian.org/debian-devel/2016/01/msg00133.html referencing the following transition bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=650601 My takeaway was the expected build dependency is the following: ... libpng-dev, ... Would not it be OK? Gianfranco, please cancel your NMU, I'll upload an updated kodi package right after libpng is updated in unstable adapting to the libpng binary package structure whatever it ends to be. Thanks, Balint
