Re: Why this rpmlint error with Perl provides

[Al Pacifico <adpacifico yahoo com>]

Jeff-
Thanks for the detailed response. However, the
solution is not yet at hand for me.

> On Sep 11, 2006, at 8:20 PM, Al Pacifico wrote:
> 
> 
>     I'm packaging a CPAN module POE::Queue and my
rpm
>     builds fine, but 'rpmlint -i
>     ../RPMS/noarch/perl-POE-Queue-0.37-1.noarch.rpm'
gives
>     the following errors:
>     E: perl-POE-Queue useless-explicit-provides
>     perl(POE::Kernel)
>     This package provides 2 times the same capacity.
It
>     should only provide it
>     once.
> 
>     E: perl-POE-Queue useless-explicit-provides
>     perl(POE::Loop::Tk)
>     This package provides 2 times the same capacity.
It
>     should only provide it
>     once.
> 
I would have guessed this was a redundant capability
provided rather than a dependency required from the
error message.

<snip>

> 
> rpmlint is complaining about a redundant dependency.
> 
> 
> There is a dependency on any perl(POE::Kernel) as
well as on a specific version.
> 
>     No other provide is listed twice, though some
list
>     with trailing numbers (what do they mean?) and
some
>     list without.
> 
> 
> Run
> 	rpm -qp --filerequire
perl-POE-Queue-0.37-1.noarch.rpm
> to find which files are generating the dependencies.
> 


Files sem to be:
$ rpm -qp --filerequire
../RPMS/noarch/perl-POE-Queue-0.37-1.noarch.rpm | grep
'perl(POE::Kernel)'/usr/lib/perl5/vendor_perl/5.8.8/POE/API/Ctl.pm
perl(Carp) perl(POE::Kernel)
perl(POE::Resource::Controls) perl(strict) perl(vars)
/usr/lib/perl5/vendor_perl/5.8.8/POE/Loop/PerlSignals.pm
       perl(POE::Kernel) perl(strict) perl(vars)

> 
>     Are these errors important? What do I do to make
them
>     go away?
> 
> 
> The errors are likely harmless.
> 
> 
> Change one of the two "use ..." statements in the
files to be like the other
> 
The use statements for 

> so that perl-req.pl extracts one, not two,
dependencies.
> 

but the use statements are exactly the same:

grep use ../BUILD/POE-0.37/lib/POE/API/Ctl.pm

use strict;
use vars qw($VERSION);
use POE::Kernel;
use POE::Resource::Controls;
use Carp qw( carp );
    use POE::API::Ctl;

grep use ../BUILD/POE-0.37/lib/POE/Loop/PerlSignals.pm

# use it without reinventing it.  This will save
maintenance and
use strict;
use vars qw($VERSION);
use strict;
use POE::Kernel;
POE::Loop::PerlSignals - plain Perl signal handlers
used by many loops

> Alternatively, you can override %__perl_requires
with a wrapper
> that looks something like this in your spec file:
<snip>

I'd prefer to patch the source, as you've recommended.
-al

__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com