Red Hat Bugzilla – Bug 202402
Missing perl-Archive-Tar Dependancy in RPM
Last modified: 2008-04-04 11:26:06 EDT
Description of problem:
The package perl-Archive-Tar is a dependancy for sa-update, shipped with latest
version of Spamasssassin
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Install SpamAssassin 3.1.* from FC5 Core
2. run sa-update
Fails to run because no Archive/Tar.pm found
sa-update should execute with no problems.
fwiw, SA treats sa-update as optional, and therefore its requirements are
optional and not set in the default spec file. FWIW, the three that sa-update
needs in addition to the normal set are: Archive::Tar, IO::Zlib, and LWP.
There's a ticket, I'd have to search for it, talking about making a separate
package for sa-update, which in that case could have all the requirements built
in. But we haven't gone that route yet.
This has been in our FC6 spec for a while now. I suppose we can push this back
into FC5 if we do a spamassassin-3.1.x update there.
I'm running fc6t3+rawhide and it still fails because of LWP:UserAgent missing:
raptor> sa-update --help
Can't locate LWP/UserAgent.pm in @INC (@INC contains:
/usr/lib/perl5/5.8.8/i386-linux-thread-multi /usr/lib/perl5/5.8.8) at
/usr/bin/sa-update line 91.
BEGIN failed--compilation aborted at /usr/bin/sa-update line 91.
Well I just installed cpan2rpm to try to build the missing perl modules and it
installed perl-libwww-perl as a requirement. That fixed sa-learn so I guess it's
just a missing Requires.
The naming of perl module rpms can be a little bit non-intuitive sometimes. I
did an intial yum search LWP and found some perl-LWP-Authen-Wsse and yet the
parent module is named perl-libwww-perl.
The right thing to do in a situation like this is "yum install
The package name follows the upstream name (with "perl-" tacked on to the
beginning), which doesn't always make sense.
Fedora apologizes that these issues have not been resolved yet. We're
sorry it's taken so long for your bug to be properly triaged and acted
on. We appreciate the time you took to report this issue and want to
make sure no important bugs slip through the cracks.
If you're currently running a version of Fedora Core between 1 and 6,
please note that Fedora no longer maintains these releases. We strongly
encourage you to upgrade to a current Fedora release. In order to
refocus our efforts as a project we are flagging all of the open bugs
for releases which are no longer maintained and closing them.
If this bug is still open against Fedora Core 1 through 6, thirty days
from now, it will be closed 'WONTFIX'. If you can reporduce this bug in
the latest Fedora version, please change to the respective version. If
you are unable to do this, please add a comment to this bug requesting
Thanks for your help, and we apologize again that we haven't handled
these issues to this point.
The process we are following is outlined here:
We will be following the process here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this
doesn't happen again.
And if you'd like to join the bug triage team to help make things
better, check out http://fedoraproject.org/wiki/BugZappers