On Thu, Feb 22, 2001 at 06:15:19PM -0700, Jason Gunthorpe wrote:
>
> On Thu, 22 Feb 2001, Sean 'Shaleh' Perry wrote:
>
> > Specifically, [!i386 m68k] seems like it could be valid, but seems to not
> > be.
> > The archs are also whitespace separated, some people are using commas.
> > Perhaps
>
On Thu, 22 Feb 2001, Sean 'Shaleh' Perry wrote:
> Specifically, [!i386 m68k] seems like it could be valid, but seems to not be.
> The archs are also whitespace separated, some people are using commas.
> Perhaps
> an exmple with multiple arches would be good.
It is supported by APT..
Python 1.
Package: debian-policy
Version: 3.5.2.0
Severity: normal
please refer to lintian bug 86710, it asks for lintian to check the syntax of
the Build-Depends field.
Specifically, [!i386 m68k] seems like it could be valid, but seems to not be.
The archs are also whitespace separated, some people are us
On Thu, Feb 22, 2001 at 02:33:59PM +0100, philippe batailler wrote:
> Package: debian-policy
> Version: 3.5.2.0
> Severity: minor
>
> -- quote
> It used to do this by calling ldd, but it
> now calls objdump to to this. This
> -- end quote
>
> to to = to do ?
Yes, I've noticed it too, and will
On Tue, 20 Feb 2001, Sean 'Shaleh' Perry wrote:
>when I rewrite lintian (started yesterday) the lintian messages will match
>policy:
>
>Error (E:) -- violate a MUST
>Warning (W:) -- violate a SHOULD
>XXX (?:) -- a MAY is not followed
Advisory (A:)?
>not sure what I am naming the MAY messag
Package: debian-policy
Version: 3.5.2.0
Severity: minor
-- quote
It used to do this by calling ldd, but it
now calls objdump to to this. This
-- end quote
to to = to do ?
6 matches
Mail list logo
