On Wed, 15 Feb 2006, Anthony DeRobertis wrote:
Policy 7.6 does, as quoted in my original report. A bigger excerpt
reads (notice the "must be satisfied"):
"The dependencies and conflicts [Build-Depends, Build-Depends-Indep,
Build-Conflicts, and Build-Conflicts-Indep] must be satisfied (as
define
On Wed, Feb 15, 2006 at 12:50:56AM -0800, Jurij Smakov wrote:
> And the policy violation justification does not
> really apply here, since nothing in policy forbids to try and build the
> package with missing build-deps.
Policy 7.6 does, as quoted in my original report. A bigger excerpt
reads (
severity 339488 important
thanks
Hi,
Sorry, but this bug is not really RC. The package is not unusable, it only
breaks in the rather corner case when the updated version introduces new
build-deps (and then there is a trivial workaround - deleting and
reinstalling the source). And the policy v
3 matches
Mail list logo
