spamassassin vs. psa-spamassassin
spamassassin vs. psa-spamassassin
What's the difference between spamassassin and psa-spamassassin?
same problem here
PSA-Spammassassin conflicts with ART Spamassassin:
what should I do to resolve this?
Code: Select all
Preparing for packages installation...
----- begin of output -----
Installing /PSA_7.5.3/rpm_FedoraCore_2/opt/mail/perl-Text-Iconv-1.2-21.i586.rpm
Installing /PSA_7.5.3/rpm_FedoraCore_2/opt/mail/psa-spamassassin-7.5.3-fc2.build75050506.13.i586.rpm
error: Failed dependencies:
psa-spamassassin conflicts with spamassassin-3.1.0-1.rhfc2.art
----- end of output -----
===> Autoinstaller: stopped logging at Sun Oct 16 09:59:54 2005
big problem
Hello Scott
When I try to install 7.5.4, I get this:
(I selected 7.5.4 update and also checked spamassassin for update/install)
I can't install Spamassassin version for 7.5.4 alone, the check in 7.5.4 base packages wont go away.
I can't update 7.5.3 because of mentioned conflict.
It seems I am in a deadlock?
When I try to install 7.5.4, I get this:
(I selected 7.5.4 update and also checked spamassassin for update/install)
Code: Select all
Preparing for packages installation...
----- begin of output -----
Installing /PSA_7.5.4/rpm_FedoraCore_2/base/psa-hotfix-7.5.4-fc2.build75050926.17.i586.rpm
Installing /PSA_7.5.4/rpm_FedoraCore_2/base/psa-7.5.4-fc2.build75050824.12.i586.rpm
Installing /PSA_7.5.4/rpm_FedoraCore_2/base/psa-api-common-7.5.4-fc2.build75050902.09.noarch.rpm
Installing /PSA_7.5.4/rpm_FedoraCore_2/base/psa-api-cli-7.5.4-fc2.build75050902.09.noarch.rpm
Installing /PSA_7.5.4/rpm_FedoraCore_2/opt/api/psa-api-rpc-7.5.4-fc2.build75050902.09.noarch.rpm
Installing /PSA_7.5.4/rpm_FedoraCore_2/opt/api/psa-agent-1.3.5-75050902.09.noarch.rpm
Installing /PSA_7.5.4/rpm_FedoraCore_2/opt/bu/psa-bu-7.5.4-fc2.build75050926.17.i586.rpm
Installing /PSA_7.5.4/rpm_FedoraCore_2/opt/docs/psa-manual-custom-skin-guide-7.5.4-fc2.build75050824.12.noarch.rpm
error: Failed dependencies:
spamassassin is needed by (installed) squirrelmail-1.4.4-4.rhfc2.art
spamassassin is needed by (installed) qmail-scanner-1.25-9.rhfc2.art
----- end of output -----
===> Autoinstaller: stopped logging at Mon Oct 17 05:43:35 2005
I can't update 7.5.3 because of mentioned conflict.
It seems I am in a deadlock?
Here's some friendly debug output from Yum:
putting spamassassin in simple update list
nulist = 124
uplist = 1
newlist = 123
obsoleting = 0
obsoleted = 0
Updating spamassassin
Resolving dependencies
Updating: spamassassin, i386
Not an install only pkg, adding to ts
Long Check
Updating: spamassassin, i386
Not an install only pkg, adding to ts
# of Deps = 1
debug dep: spamassassin req psa-spamassassin - 7.5.3 - 1<-- Eh?
conflict: spamassassin psa-spamassassin 7.5.3
Restarting Dependency Loop
.conflict between spamassassin and psa-spamassassin
putting spamassassin in simple update list
nulist = 124
uplist = 1
newlist = 123
obsoleting = 0
obsoleted = 0
Updating spamassassin
Resolving dependencies
Updating: spamassassin, i386
Not an install only pkg, adding to ts
Long Check
Updating: spamassassin, i386
Not an install only pkg, adding to ts
# of Deps = 1
debug dep: spamassassin req psa-spamassassin - 7.5.3 - 1<-- Eh?
conflict: spamassassin psa-spamassassin 7.5.3
Restarting Dependency Loop
.conflict between spamassassin and psa-spamassassin
I get the same thing when I debug during the update, even though I have psa 7.5.4 installed as well as psa-spamassassin 7.5.4.tabacco wrote: debug dep: spamassassin req psa-spamassassin - 7.5.3 - 1<-- Eh?
conflict: spamassassin psa-spamassassin 7.5.3
Restarting Dependency Loop
.conflict between spamassassin and psa-spamassassin