| Summary: | Spam Assassin depends on Digest-SH1 | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Paul McDermott <pmcdermott98> |
| Component: | Current packages | Assignee: | Gentoo Perl team <perl> |
| Status: | RESOLVED INVALID | ||
| Severity: | minor | ||
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | x86 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Paul McDermott
2005-04-09 09:52:38 UTC
Since a grep reveals: spamassassin-2.63-r1.ebuild: dev-perl/Digest-SHA1 spamassassin-2.63.ebuild: dev-perl/Digest-SHA1 spamassassin-2.64-r1.ebuild: dev-perl/Digest-SHA1 spamassassin-2.64.ebuild: dev-perl/Digest-SHA1 spamassassin-3.0.0-r1.ebuild: dev-perl/Digest-SHA1 spamassassin-3.0.0.ebuild: dev-perl/Digest-SHA1 spamassassin-3.0.1.ebuild: dev-perl/Digest-SHA1 spamassassin-3.0.2-r1.ebuild: dev-perl/Digest-SHA1 spamassassin-3.0.2.ebuild: dev-perl/Digest-SHA1 I'm going to take a stab and say you upgraded versions of perl at some point :) Two choices: re-emerge Digest-SHA1 and move along, or run perl-cleaner under $PORTDIR/dev-lang/perl/files/ and let it correct any other ebuilds you might have that had xs code linked against your old perl (there's a note about this after perl installs that can be missed at times - the output's also captured if you enable logging in make.conf). It was already in the depend list. |