rpmlint (was: review still needed: fpc)

[Tom 'spot' Callaway]

On Thu, 2005-08-04 at 21:57 +0100, Paul Howarth wrote:
> On Thu, 2005-08-04 at 15:50 -0500, Tom 'spot' Callaway wrote:
> > rpmlint output:
> > 
> > rpmlint /home/spot/rpmbuild/RPMS/i386/fpc-2.0.0-1.i386.rpm
> > E: fpc devel-dependency gpm-devel
> > W: fpc invalid-license GPL and modified LGPL
> > E: fpc statically-linked-binary /usr/lib/fpc/2.0.0/ppc386
> > E: fpc statically-linked-binary /usr/bin/ppumove
> > E: fpc statically-linked-binary /usr/bin/fpc
> > E: fpc statically-linked-binary /usr/bin/pyacc
> > E: fpc statically-linked-binary /usr/bin/unitdiff
> > E: fpc statically-linked-binary /usr/bin/fpcmkcfg
> 
> When I run rpmlint on an x86 machine against an x86_64 rpm, I get errors
> like these (statically-linked-binary) for all the binaries, even though
> they're actually dynamically linked (rpmlint run against the i386
> version of the same package is clean). Is this a known issue with
> rpmlint or should I raise a bug on it?

Go ahead and file a bug. Worst thing they can do is close it as a
dupe. :)

~spot
-- 
Tom "spot" Callaway: Red Hat Senior Sales Engineer || GPG ID: 93054260
Fedora Extras Steering Committee Member (RPM Standards and Practices)
Aurora Linux Project Leader: http://auroralinux.org
Lemurs, llamas, and sparcs, oh my!