https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6746

             Bug #: 6746
           Summary: sa-update exiting with code 4 with pt_BR.UTF-8 locale
           Product: Spamassassin
           Version: 3.3.1
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: sa-update
        AssignedTo: [email protected]
        ReportedBy: [email protected]
    Classification: Unclassified


Created attachment 5030
  --> https://issues.apache.org/SpamAssassin/attachment.cgi?id=5030
Full output with "spamassassin --lint -D" with locale as pt_BR.UTF-8

I don't know if it's related with bug 3062 but trying to run "sa-update" on a
machine with locales set to pt_BR.UTF-8 I am seeing this:

=====
config: warning: description exists for non-existent rule AWL
channel: lint check of update failed, channel failed
=====

After exporting LC_ALL=C sa-update runs fine without any message.

It's fully reproducible by setting another updatedir ("sa-update --updatedir
/tmp/updates" for example).

After trying to track the origin of this issue it was possible to see that with
locale as pt_BR.UTF-8 we can see with "spamassassin --lint":

=====
Jan  2 17:56:52.748 [15061] warn: config: warning: description exists for
non-existent rule AWL
Jan  2 17:56:53.507 [15061] warn: lint: 1 issues detected, please rerun with
debug enabled for more information
=====

while "LC_ALL=C spamassassin --lint" gives no messages.

Attached is the full output when running "spamassassin --lint -D" with locale
as pt_BR.UTF-8

Interesting to note that it gives "warn: lint: 1 issues detected, please rerun
with debug enabled for more information" when running with -D, but it doesn't
tell us where lint has failed (maybe it's necessary to have a more verbose
debug level somewhere?)

spamassasin is Debian's 3.3.1-1

I can provide more info if needed.

-- 
Configure bugmail: 
https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

Reply via email to