Am 14.09.2015 um 20:13 schrieb Matus UHLAR - fantomas:
On 12.09.15 15:27, Reindl Harald wrote:and no, i am not the package maintainer but the first person who would file a bug for *any* package which rely on a internet connection due updateAm 14.09.2015 um 17:25 schrieb Matus UHLAR - fantomas:in such case it's up to the distributions' maintainer to: - provide static rules in the (maybe separate) package - to warn user that he must immediately get new rules or the SA won't workOn 14.09.15 18:40, Reindl Harald wrote:it is a SA 3.4.1 bug that it don't start when /var/lib/spamassassin/3.004001/ while the package ships the static rules in /usr/share/spamassassin/with the original 3.4.0 setup it started just fine before sa-update as i installed all that stuff a year ago if you would have followed the thread before response you would know that alreadyI see this particular information for the first time. Maybe you could point me to proper place in the archive? Or maybe you could be more specific instead of blame everyone for everything?
-------- Weitergeleitete Nachricht --------
Betreff: Re: Live upgrade safe?
Datum: Mon, 14 Sep 2015 01:44:25 +0200
Von: Reindl Harald <h.rei...@thelounge.net>
An: users@spamassassin.apache.org
Am 14.09.2015 um 01:41 schrieb Reindl Harald:
>
>
> Am 14.09.2015 um 01:35 schrieb Greg Troxel:
>> Reindl Harald <h.rei...@thelounge.net> writes:
>>
>>> RPM packages are not supposed to contact network *3rd party*
>>> ressources at install time and when you think 1 second you know why -
>>> who tells you that the 3rd party ressource is available at that moment
>>> and how handle errors and bugreports when it fails?
>>>
>>> that will never happen in a distribution package - no idea why you
>>> think we need to discuss that or even you can consider something as
>>> bug when you obviously have no expierience with distributions..
>>
>> In pkgsrc, it is also considered a bug for a package installation to use
>> the net. Our spamassassin package doesn't, and users have to run
>> sa-update before starting it after upgrades. This seems broken to me;
>> it seems that a release should come with rules, even if we know that
>> people should be updating to more modern ones. This seems to be a
>> recent change; I don't remember getting bit by it until just now.
>
> it *comes* with rules but at least with 3.4.1 there where crashes
> without reported running "sa-update", there are always the default
> scores and rules besides /var/lib/spamassassin
here you go - /var/lib/spamassassin/3.004001/ empty and it fails to start
[root@testserver:~]$ rm -rf /var/lib/spamassassin/3.004001/*
[root@testserver:~]$ systemctl restart spamassassin.service
[root@testserver:~]$ cat messages
Sep 14 01:00:31 testserver systemd: Stopping Spamassassin Daemon...
Sep 14 01:00:31 testserver systemd: Starting Spamassassin Daemon...
Sep 14 01:00:31 testserver systemd: Started Spamassassin Daemon.
Sep 14 01:37:00 testserver su: (to builduser) root on pts/1
Sep 14 01:42:43 testserver systemd: Stopping Spamassassin Daemon...
Sep 14 01:42:43 testserver systemd: Starting Spamassassin Daemon...
Sep 14 01:42:43 testserver systemd: Started Spamassassin Daemon.
Sep 14 01:42:44 testserver systemd: spamassassin.service: main process
exited, code=exited, status=255/n/a
Sep 14 01:42:44 testserver systemd: Unit spamassassin.service entered
failed state.
Sep 14 01:42:44 testserver systemd: spamassassin.service failed.
Sep 14 01:42:45 testserver systemd: spamassassin.service holdoff time
over, scheduling restart.
Sep 14 01:42:45 testserver systemd: Starting Spamassassin Daemon...
Sep 14 01:42:45 testserver systemd: Started Spamassassin Daemon.
Sep 14 01:42:45 testserver systemd: spamassassin.service: main process
exited, code=exited, status=255/n/a
Sep 14 01:42:45 testserver systemd: Unit spamassassin.service entered
failed state.
Sep 14 01:42:45 testserver systemd: spamassassin.service failed.
[root@testserver:~]$
____________________________________________________
after "sa-update" all is fine
[root@testserver:~]$ sa-update
[root@testserver:~]$ systemctl restart spamassassin.service
[root@testserver:~]$ systemctl status spamassassin.service
● spamassassin.service - Spamassassin Daemon
Loaded: loaded (/etc/systemd/system/spamassassin.service; enabled;
vendor preset: disabled)
Active: active (running) since Mo 2015-09-14 01:43:47 CEST; 10s ago
Process: 103996 ExecStartPre=/usr/bin/find /var/lib/spamassassin/
-type f -exec /bin/chmod 0644 {} ; (code=exited, status=0/SUCCESS)
Process: 103991 ExecStartPre=/usr/bin/find /var/lib/spamassassin/
-type d -exec /bin/chmod 0755 {} ; (code=exited, status=0/SUCCESS)
Main PID: 104066 (spamd)
> rpm -q --filesbypkg spamassassin | grep /usr/share/spamassassin/
> spamassassin /usr/share/spamassassin/10_default_prefs.cf
> spamassassin /usr/share/spamassassin/10_hasbase.cf
> spamassassin /usr/share/spamassassin/20_advance_fee.cf
> spamassassin /usr/share/spamassassin/20_aux_tlds.cf
> spamassassin /usr/share/spamassassin/20_body_tests.cf
> spamassassin /usr/share/spamassassin/20_compensate.cf
> spamassassin /usr/share/spamassassin/20_dnsbl_tests.cf
> spamassassin /usr/share/spamassassin/20_drugs.cf
> spamassassin /usr/share/spamassassin/20_dynrdns.cf
> spamassassin /usr/share/spamassassin/20_fake_helo_tests.cf
> spamassassin /usr/share/spamassassin/20_freemail.cf
> spamassassin /usr/share/spamassassin/20_freemail_domains.cf
> spamassassin /usr/share/spamassassin/20_freemail_mailcom_domains.cf
> spamassassin /usr/share/spamassassin/20_head_tests.cf
> spamassassin /usr/share/spamassassin/20_html_tests.cf
> spamassassin /usr/share/spamassassin/20_imageinfo.cf
> spamassassin /usr/share/spamassassin/20_mailspike.cf
> spamassassin /usr/share/spamassassin/20_meta_tests.cf
> spamassassin /usr/share/spamassassin/20_net_tests.cf
> spamassassin /usr/share/spamassassin/20_pdfinfo.cf
> spamassassin /usr/share/spamassassin/20_phrases.cf
> spamassassin /usr/share/spamassassin/20_porn.cf
> spamassassin /usr/share/spamassassin/20_ratware.cf
> spamassassin /usr/share/spamassassin/20_uri_tests.cf
> spamassassin /usr/share/spamassassin/20_vbounce.cf
> spamassassin /usr/share/spamassassin/23_bayes.cf
> spamassassin /usr/share/spamassassin/25_accessdb.cf
> spamassassin /usr/share/spamassassin/25_antivirus.cf
> spamassassin /usr/share/spamassassin/25_asn.cf
> spamassassin /usr/share/spamassassin/25_dcc.cf
> spamassassin /usr/share/spamassassin/25_dkim.cf
> spamassassin /usr/share/spamassassin/25_hashcash.cf
> spamassassin /usr/share/spamassassin/25_pyzor.cf
> spamassassin /usr/share/spamassassin/25_razor2.cf
> spamassassin /usr/share/spamassassin/25_replace.cf
> spamassassin /usr/share/spamassassin/25_spf.cf
> spamassassin /usr/share/spamassassin/25_textcat.cf
> spamassassin /usr/share/spamassassin/25_uribl.cf
> spamassassin /usr/share/spamassassin/30_text_de.cf
> spamassassin /usr/share/spamassassin/30_text_fr.cf
> spamassassin /usr/share/spamassassin/30_text_it.cf
> spamassassin /usr/share/spamassassin/30_text_nl.cf
> spamassassin /usr/share/spamassassin/30_text_pl.cf
> spamassassin /usr/share/spamassassin/30_text_pt_br.cf
> spamassassin /usr/share/spamassassin/50_scores.cf
> spamassassin
/usr/share/spamassassin/60_adsp_override_dkim.cf
> spamassassin /usr/share/spamassassin/60_awl.cf > spamassassin /usr/share/spamassassin/60_shortcircuit.cf > spamassassin /usr/share/spamassassin/60_whitelist.cf > spamassassin /usr/share/spamassassin/60_whitelist_dkim.cf > spamassassin /usr/share/spamassassin/60_whitelist_spf.cf > spamassassin /usr/share/spamassassin/60_whitelist_subject.cf > spamassassin /usr/share/spamassassin/72_active.cf > spamassassin /usr/share/spamassassin/72_scores.cf > spamassassin /usr/share/spamassassin/73_sandbox_manual_scores.cf > spamassassin /usr/share/spamassassin/STATISTICS-set0-72_scores.cf.txt > spamassassin /usr/share/spamassassin/STATISTICS-set1-72_scores.cf.txt > spamassassin /usr/share/spamassassin/STATISTICS-set2-72_scores.cf.txt > spamassassin /usr/share/spamassassin/STATISTICS-set3-72_scores.cf.txt > spamassassin /usr/share/spamassassin/languages > spamassassin /usr/share/spamassassin/local.cf > spamassassin /usr/share/spamassassin/regression_tests.cf > spamassassin /usr/share/spamassassin/sa-update-pubkey.txt > spamassassin /usr/share/spamassassin/sa-update.cron > spamassassin /usr/share/spamassassin/user_prefs.template
signature.asc
Description: OpenPGP digital signature
