Re: Missing Build-Conflicts for non-clean build environments: RC? (was: Re: Bug#508947: Lowering severity)
On Sat, Dec 20, 2008 at 10:12:48AM +0000, Sune Vuorela wrote:
> >> I don't agree with your arguing. Serious is defined as "severe violation
> >> of Debian policy (roughly, it violates a "must" or "required"
> >> directive)". Debian policy 7.7 says:=20
> >> |Build-Depends, Build-Conflicts
> >> | The Build-Depends and Build-Conflicts fields must be satisfied when
> >> |any of the following targets is invoked: build, clean, binary,
> >> |binary-arch, build-arch, build-indep and binary-indep.
> >> It does not mention a clean chroot. Afaik it also violates the policy if
> >> a packages build in fully installed chroot ist linked against
> >> more/different libraries than the same package build in a clean chroot.
> Up to the etch release, I asked release people wether missing
> build-dependencies was release critical. They said no.
Packages must list any packages they require to build beyond those
that are "build-essential" in the appropriate Build-Depends: fields.
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developer http://www.debian.org/