Bug 202402 - Missing perl-Archive-Tar Dependancy in RPM
Summary: Missing perl-Archive-Tar Dependancy in RPM
Alias: None
Product: Fedora
Classification: Fedora
Component: spamassassin
Version: 5
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Warren Togami
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2006-08-14 06:28 UTC by Scott Ryan
Modified: 2008-04-04 15:26 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2008-04-04 15:26:06 UTC
Type: ---

Attachments (Terms of Use)

System ID Priority Status Summary Last Updated
SpamAssassin 4997 None None None Never

Description Scott Ryan 2006-08-14 06:28:52 UTC
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):

How reproducible:

Steps to Reproduce:
1. Install SpamAssassin 3.1.* from FC5 Core
2. run sa-update
Actual results:
Fails to run because no Archive/Tar.pm found

Expected results:
sa-update should execute with no problems.

Additional info:

Comment 1 Theo Van Dinter 2006-08-14 13:45:50 UTC
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.

Comment 2 Warren Togami 2006-08-14 14:57:56 UTC
Requires: perl(Archive::Tar)

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.

Comment 3 Thomas J. Baker 2006-10-19 12:59:24 UTC
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/site_perl/5.8.8 /usr/lib/perl5/site_perl/5.8.7
/usr/lib/perl5/site_perl/5.8.6 /usr/lib/perl5/site_perl/5.8.5
/usr/lib/perl5/vendor_perl/5.8.7 /usr/lib/perl5/vendor_perl/5.8.6
/usr/lib/perl5/vendor_perl/5.8.5 /usr/lib/perl5/vendor_perl
/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.

Comment 4 Thomas J. Baker 2006-10-19 13:09:56 UTC
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.

Comment 5 Steven Pritchard 2006-10-19 16:25:22 UTC
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.

Comment 6 Bug Zapper 2008-04-04 03:31:55 UTC
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
the change.

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

Note You need to log in before you can comment on or make changes to this bug.