http://issues.apache.org/SpamAssassin/show_bug.cgi?id=5354
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
OS/Version|other |Mac OS X
Platform|Other |Macintosh
------- Additional Comments From [EMAIL PROTECTED] 2007-03-07 03:09 -------
(In reply to comment #14)
> On my MacOS 10.4.8 on an Intel MacBook, without the extra ruleset, when I try
> sa-compile --sudo -D using svn trunk I get to the end
Which is good -- I suggest you and snowcrash now compare perl/library
versions... ;)
You could also try using the additional rulesets: I've tarred them up
at http://taint.org/x/2007/bug5354-all-rulesets.tgz to save you downloading
each one. Note though that this works fine for me with those sets on
linux (aside from the different bug in RE compilation later).
> sudo rm -rf /tmp/.spamassassin13558foZOGptmp
> rm: fts_read: No such file or directory
> command failed! at /usr/bin/sa-compile line 236.
>
> Google found nothing that helped regarding the "rm: fts_read: No such file or
> directory" message. When I tried on the command line sudo rm -rf
> /tmp/.spamassassin13558foZOGptmp it worked ok.
http://developer.apple.com/documentation/Darwin/Reference/Manpages/man3/fts_read.3.html
The functions fts_read() and fts_children() may fail and set errno for
any of the errors specified for the library functions chdir(2),
malloc(3), opendir(3), readdir(3) and stat(2).
Wierd. The only thing I can think of is that something else
deleted the dir while the "rm" was proceeding, but you're saying
the directory was still there afterwards?
Can you trace it using strace/truss/ftrace or whatever the MacOS
equivalent is?
(PS: Loren:
> FWIW, we have indications that SARE_ADULT is *very* unhappy on 3.2, getting
> hundreds of syntax errors that were never there before. Seems to be related
> to
> high-bit characters in the obfuscation REs.
SARE_ADULT1 or SARE_ADULT2? a rule called "SARE_ADULT" isn't showing up
in the rules from the updates channel. Sounds like a UTF-8 problem though...
but this is a separate issue and should not be followed up in this bug.)
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
