Remco, That was a bug in trunk. And your package appears to be based on trunk not the 3.3.2 release. You might have them try the sa-update from trunk. Regards, KAM
Remco Rijnders <[email protected]> wrote: Dear all, I foolishly volunteered to be the package maintainer for spamassassin in the Mageia Linux distribution. As I'm quite new to this, please bear with me and I apologise up front if this message should have been sent to the users-list instead. Anyways, a bug was reported by one of our users that sa-update is not working properly (anymore). See the bug report he opened at https://bugs.mageia.org/show_bug.cgi?id=3814 A quick scan and search did not turn up any Mageia specific changes that would explain for the observed behaviour. As I see there have been recent changes (recent as in <3 months) in the way updates are handled, I wondered if this is a broader problem than just with the version as shipped in Mageia? In one of the comments to the bug report I also propose a possible work around for this problem. Do you concur this is the proper fix to version 3.3.2 for this problem? I'm also a little puzzled why it checks for updates to version 3.4.0 when that does not match the version installed on the user's system. Am I on the right track here, or chasing a red herring? Thanks in advance, Remco
