[pkg-php-pear] phing_2.7.0+dfsg-1_amd64.changes REJECTED

Ansgar Burchardt ansgar at debian.org
Tue Sep 2 14:09:09 UTC 2014

On 09/02/2014 16:01, David Prévot wrote:
> Le 02/09/2014 09:22, Ansgar Burchardt a écrit :
>> Policy 2.2.1:
>>    In addition, the packages in main
>>       must not require or recommend a package outside of main for
>>       compilation or execution (thus, the package must not declare a
>>       "Pre-Depends", "Depends", "Recommends", "Build-Depends", or
>>       "Build-Depends-Indep" relationship on a non-main package),
> This part is in the context of the archive area, and the nonexisting
> packages are de facto not available in an archive area outside of main.

Every nonexisting package is especially a package outside of main.

You can also just use "Depends" for the paragraph I quoted. Packages in
main must especially not depend on nonexisting packages. :)

>>> Many packages in the archive have unsatisfiable recommends, that is not
>>> a policy violation, that works fine, and doesn’t warrant any RC bugs, so
>>> I’m quite surprised by this rejection.
>> That's a bug then.
> I believe it’s a bug in the way the policy is currently worded, and may
> raise one, to make it clear what the actual intent is.

I'm fairly sure it's not: as you quoted, recommended packages are
supposed to be installed in "all but unusual installations". Having
recommended packages not installable means all installations would
suddenly be "unusual" installations. That would not make sense to me.

> I’d like to get
> some number before doing so, do you have any advice on how to spot all
> recommended packages that are unsatisfiable in a given suite?

For each recommended package check if it exists? (This includes being
provided by some other packge.)


More information about the pkg-php-pear mailing list