[pmg-devel] [PATCH spamassassin 1/9] do not ship config-files rendered from templates

Stoiko Ivanov s.ivanov at proxmox.com
Mon Jan 20 19:37:27 CET 2020

while upgrading spamassassin from 3.4.2 to 3.4.3 users were initially asked
to confirm a changed '/etc/mail/spamassassin/init.pre', due to the differences
between the file in the shipped new upstream and the version rendered by the
templateing system of pmg.
This was mitigated by c0e5b8043c8ff69bc909f8b7ae128f9b5ed27e47.

Not shipping the files in the first place removes the need to adapt changed
upstream files to old versions, which get replaced by the templating system

Signed-off-by: Stoiko Ivanov <s.ivanov at proxmox.com>
 debian/rules | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/debian/rules b/debian/rules
index 9f8bb83..24da61b 100755
--- a/debian/rules
+++ b/debian/rules
@@ -63,6 +63,11 @@ install-stamp:
 	# rm example local.cf
 	rm $(TMP)/etc/mail/spamassassin/local.cf
+	# rm config files rendered by PMG templates
+	rm $(TMP)/etc/mail/spamassassin/init.pre
+	rm $(TMP)/etc/mail/spamassassin/v310.pre
+	rm $(TMP)/etc/mail/spamassassin/v320.pre
 	# apply rule updates
 	tar xzvf ../sa-updates.tgz -C $(TMP)/usr/share/spamassassin/
 	#patch -d $(TMP)/usr/share/spamassassin <../72_active.cf.diff

More information about the pmg-devel mailing list