Bug 19491 - When updating from Spam Assassin 3.4.0 to 3.4.1 I get Errors when reporting spam
Summary: When updating from Spam Assassin 3.4.0 to 3.4.1 I get Errors when reporting spam
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 5
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: QA Team
QA Contact:
URL:
Whiteboard: advisory MGA5-64-OK MGA5-32-OK
Keywords: validated_update
Depends on:
Blocks:
 
Reported: 2016-09-30 01:07 CEST by Sleepy Z
Modified: 2016-10-18 20:44 CEST (History)
5 users (show)

See Also:
Source RPM: spamassassin-rules-3.3.2-5.mga5.src.rpm
CVE:
Status comment:


Attachments

Description Sleepy Z 2016-09-30 01:07:26 CEST
Description of problem: When upgrading from SA 3.4.0 to 3.4.1

config: configuration file "/usr/share/spamassassin/20_advance_fee.cf" requires version 3.004000 of SpamAssassin, but this is code version 3.004001. Maybe you need to use the -C switch, or remove the old config files? Skipping this file at /usr/share/perl5/vendor_perl/Mail/SpamAssassin/Conf/Parser.pm line 406.


Version-Release number of selected component (if applicable):
Spam Assassin 3.4.1
Spam Assassin Rules 
 Version: 3.3.2-5.mga5
        Currently installed version: 3.3.2-5.mga5
        Group: Networking/Mail
        Architecture: noarch
        Size: 709 KB
        Medium: None (installed)

How reproducible: Do the update from SA 3.4.0 to 3.4.1

I believe the issue is with the rules are not updated and are not compatiable with the lastest version of SA


Steps to Reproduce:
1.
2.
3.
Sleepy Z 2016-09-30 01:08:23 CEST

URL: http://spamassassin.apache.org/ => (none)

Comment 1 Marja Van Waes 2016-09-30 15:12:59 CEST
I'm confused.

Going by its changelog, spamassassin-3.4.1-2.mga5 is needed to correctly require the matching spamassassin-rules package.

However, spamassassin-3.4.1-2.mga5 is still in updates_testing, and QA team is not testing it :-(
spamassassin-rules-3.4.1-1.mga5 is still in updates_testing, too.

http://mageia.webconquest.com/distrib/5/x86_64/media/core/updates_testing/

which version of spamassassin-rules do you have?

Could you try whether the spamassassin packages from updates_testing work better?

CC: (none) => marja11
Assignee: bugsquad => remco
Source RPM: Version: 3.4.1-1.mga5 Currently installed version: 3.4.0-5.mga5 Group: Networking/Mail Architecture: x86_64 Size: 507 KB Medium: Core Updates URL: => spamassassin-3.4.1-1.mga5

Comment 2 Sleepy Z 2016-09-30 22:24:21 CEST
Ok I downloaded and installed the SA Rules 3.4.1 and it updated the other components.. and its now working.


Just wonder why the SA rules update  wasn't included along with the other SA component updates
Comment 3 James Kerr 2016-09-30 23:53:21 CEST
It looks as though remmy rebuilt spamassassin on March 30th, to provide an updated rules package, but did not assign the rebuilt packages to QA, hence they were never pushed to updates.

https://ml.mageia.org/l/arc/changelog/2016-03/msg03080.html
https://ml.mageia.org/l/arc/changelog/2016-03/msg03078.html

Also see bug16308,comment25

CC: (none) => jim

Comment 4 Sleepy Z 2016-09-30 23:59:13 CEST
Thank you for all your help. I started using Mandrake and love what you all have done with Mageia..
Comment 5 David Walser 2016-10-01 16:55:13 CEST
Could someone please write an advisory and assign this to QA?

Source RPM: spamassassin-3.4.1-1.mga5 => spamassassin-rules-3.3.2-5.mga5.src.rpm

Comment 6 James Kerr 2016-10-02 08:59:42 CEST
Suggested advisory

******************************************************************
Updated spamassassin packages include compatible rules package

The previous spamassassin update did not include a compatible
spamassassin-rules package, which resulted in spamassassin failing
to function properly. This update rectifies that omission.

References:
https://bugs.mageia.org/show_bug.cgi?id=19491
http://advisories.mageia.org/MGAA-2016-0036.html

SRPMS:
spamassassin-3.4.1-2.mga5.src.rpm
spamassassin-rules-3.4.1-1.mga5.src.rpm

*******************************************************************

Packages in core/updates_testing

spamassassin-3.4.1-2.mga5.x86_64.rpm
spamassassin-rules-3.4.1-1.mga5.noarch.rpm
spamassassin-sa-compile-3.4.1-2.mga5.x86_64.rpm
spamassassin-spamc-3.4.1-2.mga5.x86_64.rpm
spamassassin-spamd-3.4.1-2.mga5.x86_64.rpm
spamassassin-tools-3.4.1-2.mga5.x86_64.rpm

spamassassin-3.4.1-2.mga5.i586.rpm
spamassassin-rules-3.4.1-1.mga5.noarch.rpm
spamassassin-sa-compile-3.4.1-2.mga5.i586.rpm
spamassassin-spamc-3.4.1-2.mga5.i586.rpm
spamassassin-spamd-3.4.1-2.mga5.i586.rpm
spamassassin-tools-3.4.1-2.mga5.i586.rpm

Assignee: remco => qa-bugs

Comment 7 James Kerr 2016-10-02 09:43:01 CEST
Sorry I missed two packages

Corrected list of packages in core/updates_testing:

x86_64

spamassassin-3.4.1-2.mga5.x86_64.rpm
spamassassin-rules-3.4.1-1.mga5.noarch.rpm
spamassassin-sa-compile-3.4.1-2.mga5.x86_64.rpm
spamassassin-spamc-3.4.1-2.mga5.x86_64.rpm
spamassassin-spamd-3.4.1-2.mga5.x86_64.rpm
spamassassin-tools-3.4.1-2.mga5.x86_64.rpm
perl-Mail-SpamAssassin-3.4.1-2.mga5.x86_64.rpm
perl-Mail-SpamAssassin-Spamd-3.4.1-2.mga5.x86_64.rpm

i586

spamassassin-3.4.1-2.mga5.i586.rpm
spamassassin-rules-3.4.1-1.mga5.noarch.rpm
spamassassin-sa-compile-3.4.1-2.mga5.i586.rpm
spamassassin-spamc-3.4.1-2.mga5.i586.rpm
spamassassin-spamd-3.4.1-2.mga5.i586.rpm
spamassassin-tools-3.4.1-2.mga5.i586.rpm
perl-Mail-SpamAssassin-3.4.1-2.mga5.i586.rpm
perl-Mail-SpamAssassin-Spamd-3.4.1-2.mga5.i586.rpm
Comment 8 Herman Viaene 2016-10-07 14:36:52 CEST
MGA5-32 on Acer D620 Xfce
When trying to select spamassassin-3.4.1-2 in MCC, I get: "- spamassassin-3.4.1-2.mga5.i586 (vanwege onvoldane spamassassin-rules[>= 3.4.1]) 
because of unfulfilled ......

CC: (none) => herman.viaene

Comment 9 Marja Van Waes 2016-10-07 16:44:51 CEST
(In reply to Herman Viaene from comment #8)
> MGA5-32 on Acer D620 Xfce
> When trying to select spamassassin-3.4.1-2 in MCC, I get: "-
> spamassassin-3.4.1-2.mga5.i586 (vanwege onvoldane spamassassin-rules[>=
> 3.4.1]) 
> because of unfulfilled ......

spamassassin-rules should be available on your mirror in a matching version:

ftp://mageia.webconquest.com/distrib/5/i586/media/core/updates_testing/spamassassin-rules-3.4.1-1.mga5.noarch.rpm

Can you start MCC from a terminal like this

     LC_ALL=C mcc

And then attach the full (English) error message?
Comment 10 Herman Viaene 2016-10-08 11:47:20 CEST
Installation problem does not occur anymore.
Trying to figure out how to test ????
Made sure spamd is running, sent gtube test message from other account (on other PC) to my hotmail account reading with Tbird on test laptop. Message arrives as normal message, nothing in spamassasin log.
Is this the right way to test???
Nicolas Lécureuil 2016-10-12 11:20:32 CEST

CC: (none) => mageia
Whiteboard: (none) => advisory

Comment 11 James Kerr 2016-10-17 14:21:24 CEST
I installed spamasassin and then updated:
urpmi --search-media "Core Updates Testing" spamassassin
To satisfy dependencies, the following packages are going to be installed:
  Package                        Version      Release       Arch    
(medium "Core Updates Testing (LAN5)")
  spamassassin                   3.4.1        2.mga5        x86_64  
  spamassassin-rules             3.4.1        1.mga5        noarch 

Which means that the updated rules package was selected.
Packages installed cleanly.

I'm not able to test further since my ISP removes all spam before it reaches me, but based on this test and Comment#2, I have ok'd for mga5-64

(The only purpose of this update is to ensure that the updated rules package is installed.)

Whiteboard: advisory => advisory MGA5-64-OK

Comment 12 James Kerr 2016-10-17 14:39:50 CEST
On mga5-32 I installed spamassassin and then updayed

urpmi --searchmedia "Core Updates Testing" spamassassin
To satisfy dependencies, the following packages are going to be installed:
  Package                        Version      Release       Arch    
(medium "Core Updates Testing (LAN5)")
  spamassassin                   3.4.1        2.mga5        i586    
  spamassassin-rules             3.4.1        1.mga5        noarch  

Which means that the updated rules package was selected.

Packages installed cleanly.

Since the only purpose of this update is to ensure that the updated rules package is installed, I have ok'd for mga5-32.

Whiteboard: advisory MGA5-64-OK => advisory MGA5-64-OK MGA5-32-OK

Comment 13 James Kerr 2016-10-17 14:43:35 CEST
This update is now validated and can be pushed to updates.

Keywords: (none) => validated_update
CC: (none) => sysadmin-bugs

Comment 14 Mageia Robot 2016-10-18 20:44:19 CEST
An update for this issue has been pushed to the Mageia Updates repository.

http://advisories.mageia.org/MGAA-2016-0124.html

Status: NEW => RESOLVED
Resolution: (none) => FIXED


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