Re: Policy ambiguity regarding control files

["John R. Daily" <john@geekhavoc.com>]

There's seemingly a broader issue here, too. I've come across an
entry in Sources (vlc) which swaps the version and architecture
components in a build-dep line:

Build-Depends: debhelper (>=2.2.0),
               xlibs-dev,
               ...
               libasound2-dev [alpha arm hppa i386 ia64 m68k mips mipsel powerpc s390 sparc] (>=0.9.0beta7)

Ignoring the issue of whether listing 11 architectures that are
relevant is better than including the 1(?) that doesn't, why
aren't these entries checked for policy-compliance before being
accepted by the archive-management tools?

If the answer is "Because we don't have the software to do so", I
may be able to help with that soon.

-John




-- 
To UNSUBSCRIBE, email to debian-policy-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org