Re: Rules UPDATE version 1732039 IS BROKEN

[Reindl Harald <h....@thelounge.net>]

Am 25.02.2016 um 19:25 schrieb John Hardin:
>>>  If that's indeed the cause, I'm surprised that masscheck proceeded
>>> in the
>>>  face of a failed lint and that an error in one standalone rule
>>> affected a
>>>  bunch of totally unrelated rules...
>>
>> Hmmm, well, I guess a big enough problem won't fail lint:
>>
>> bigsky:spamassassin root# ls -l
>> 3.004001/updates_spamassassin_org/72_active.cf
>> -rw-r--r--  1 root  admin  0 Feb 25 04:29
>> 3.004001/updates_spamassassin_org/72_active.cf
>>
>> That's what backups are for.  :)
>> (Subject revised)
>
> Ugh.
>
> Would you file a bug so that we don't lose track of this? Thanks

tonight sa-update on all Fedora systems failed
*where* do it suddenly want write permissions?

Feb 26 01:41:53 mail-gw sa-update.cron: config: warning: description 
exists for non-existent rule EXCUSE_24
Feb 26 01:41:53 mail-gw sa-update.cron: channel: lint check of update 
failed, channel failed
Feb 26 01:41:53 mail-gw sa-update.cron: 26-Feb-2016 01:41:53: 
SpamAssassin: Update available, but download or extract failed
Feb 26 01:41:53 mail-gw systemd: sa-update.service: main process exited, 
code=exited, status=4/NOPERMISSION
Feb 26 01:41:53 mail-gw systemd: Unit sa-update.service entered failed 
state.
Feb 26 01:41:53 mail-gw systemd: sa-update.service failed.