Summary: | spamassassin-3.1.0-r2 fails with perl-error | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Dead Schorsch <spamlover> |
Component: | Current packages | Assignee: | Net-Mail Packages <net-mail+disabled> |
Status: | VERIFIED FIXED | ||
Severity: | normal | CC: | johncox, perl |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Dead Schorsch
2005-11-27 03:20:58 UTC
The weird thing is, you're USEing berkdb so perl-core/DB_File should be dragged in as a dependency without issue. I wonder what happens if you try: emerge --oneshot perl-core/DB_File emerge spamassassin Looks like your sys-libs/db install is somewhat broken - see Bug 85727. As for comment #1: DB_File emerges, but that does not affect the outcome of emerge spamassassin. Still does fail. As for comment #2, I had to change the symlink db.h to version 4.2 manually, after that, SpamAssassing emerged. As for sys-lib/db: why is it, that $ emerge --search db displays * sys-libs/db Latest version available: 4.2.52_p2 Latest version installed: 4.2.52_p2 while $ emerge --prune sys-lib/db displays sys-libs/db selected: 4.0.14-r2 4.1.25_p1-r4 4.2.52_p2 1.85-r3 protected: 3.2.9-r10 omitted: none What makes emerge want to remove the newer versions and keep 3.2 series? Christoph (In reply to comment #4) > As for comment #2, I had to change the symlink db.h to version 4.2 manually, > after that, SpamAssassing emerged. Thanks for reporting back. > What makes emerge want to remove the newer versions and keep 3.2 series? emerge prune does not handle slots and you definitely should *not* unmerge the other sys-libs/db versions. This is a separate issue anyway, this bug can be probably closed. Indeed, can be closed. Thanks for assistance. Approved. *** Bug 125888 has been marked as a duplicate of this bug. *** (In reply to comment #8) > *** Bug 125888 has been marked as a duplicate of this bug. *** > I eventually re-emerged db, then DB_file, and then spamassassin, in that order and spamd started. I had no clue that db was involved. Is there something that should be added into the emerge to require that db get updated? Some change could greatly assist those of us who are marginally competent in this area. Thanks for the help. db isn't a 100% requiement for spamassassin to work - just to avoid some misleading error messages. the dep is visible if you emerge -av spamassassin (db is one of the use flags). |