Package: spamassassin / 4.0.1+svn1923525-1
Metadata
Package | Version | Patches format |
---|---|---|
spamassassin | 4.0.1+svn1923525-1 | 3.0 (quilt) |
Patch series
view the series filePatch | File delta | Description |
---|---|---|
10_change_config_paths | (download) |
INSTALL |
2 1 + 1 - 0 ! |
--- |
20_edit_spamc_pod | (download) |
spamc/spamc.pod |
2 1 + 1 - 0 ! |
--- |
55_disable_nagios_epm | (download) |
sa-check_spamd.raw |
5 5 + 0 - 0 ! |
--- |
90_pod_cleanup | (download) |
lib/Mail/SpamAssassin/Conf.pm |
2 1 + 1 - 0 ! |
--- |
debian_gitignore | (download) |
.gitignore |
50 50 + 0 - 0 ! |
--- |
bug426031 pod fix | (download) |
spamassassin.raw |
22 1 + 21 - 0 ! |
update site-specific configuration path in man page In Debian, there is exactly one site-specific configuration directory, and it is known in advance. So we can safely remove the list of possible paths from the man page in order to avoid confusion. |
skip_config_tree_recurse_test | (download) |
t/config_tree_recurse.t |
4 3 + 1 - 0 ! |
skip config_tree_recurse test The default behavior of File::Find will automatically untaint directories with "safe" names. The '~' (tilde) character is not considered a safe name. Because Debian source package names use '~' to denote pre-release versions, the test will fail with a message similar to the following: . t/config_tree_recurse.t ........... _get_cf_pre_files_in_dir error: directory /home/admin/spamassassin-3.4.3~rc6+1/t/log/localrules.tmp is still tainted at /usr/share/perl/5.30/File/Find.pm line 558. at ../lib/Mail/SpamAssassin.pm line 2096. . The solution to this is either to modify lib/Mail/SpamAssassin.pm to consider '~' a safe character, or skip the test altogether. Because the former would impact all installations, and the latter is limited to test coverage, we will skip the test. |
use_utf8_encoding.patch | (download) |
lib/Mail/SpamAssassin/Util.pm |
2 1 + 1 - 0 ! |
--- |
add ip configuration debug.patch | (download) |
t/SATest.pm |
6 6 + 0 - 0 ! |
add some debug output to tests Tests are failing on Debian buildd hosts with IPv6-only network configuration. However, I've been unable to reproduce this outside the buildd environment. Adding some debugging output to try to collect more details. . This patch can be dropped when the sitution is resolved. |
spamd_disable_ai_addrconfig_for_ipv4_literals.patch | (download) |
spamd/spamd.raw |
22 15 + 7 - 0 ! |
disable ai_addrconfig when passing ipv4 literals to getaddrinfo AI_ADDRCONFIG skips the loopback interface, but if it's the only one with IPv4 addresses configured, then it won't be returned by getaddrinfo and spamd won't end up listening anywhere. . |