If I try to upgrade my spamassassin from verion 3.4.2 to 3.4.2_1 it breaks completely with the following error message: [1/16] Upgrading spamassassin from 3.4.2 to 3.4.2_1... ===> Creating groups. Using existing group 'spamd'. ===> Creating users Using existing user 'spamd'. [1/16] Extracting spamassassin-3.4.2_1: 100% You may need to manually remove /usr/local/etc/mail/spamassassin/init.pre if it is no longer needed. You may need to manually remove /usr/local/etc/mail/spamassassin/local.cf if it is no longer needed. You may need to manually remove /usr/local/etc/mail/spamassassin/v310.pre if it is no longer needed. You may need to manually remove /usr/local/etc/mail/spamassassin/v312.pre if it is no longer needed. You may need to manually remove /usr/local/etc/mail/spamassassin/v320.pre if it is no longer needed. You may need to manually remove /usr/local/etc/mail/spamassassin/v330.pre if it is no longer needed. You may need to manually remove /usr/local/etc/mail/spamassassin/v340.pre if it is no longer needed. You may need to manually remove /usr/local/etc/mail/spamassassin/v341.pre if it is no longer needed. You may need to manually remove /usr/local/etc/mail/spamassassin/v342.pre if it is no longer needed. pkg: Fail to rename /usr/local/etc/mail/spamassassin/sa-update-keys/.gpg.conf.s8n4wuZXJTwV -> /usr/local/etc/mail/spamassassin/sa-update-keys/gpg.conf:No such file or directory Maybe related to r484326?
I have only the message if I delete the package, not if I install it 1/1] Deinstalling spamassassin-3.4.2_1... [1/1] Deleting files for spamassassin-3.4.2_1: 4% spamassassin-3.4.2_1: missing file /usr/local/etc/mail/spamassassin/sa-update-keys/gpg.conf [1/1] Deleting files for spamassassin-3.4.2_1: 100% But the file was installed.
When attempting to install mail/spamassassin from a package, this error is fatal. As per pkg-upgrade(8), using the -I option to not execute any {pre,post}-{de,}install scripts, the package can at least be upgraded successfully (would not expect a new install to work though). Could the @preunexec command which simply deletes the parent directory just above sa-update-keys/gpg.conf in the packing list be interfering with the installation and upgrade process?
I disabled now the GNUPG2 option, that fixed it for now. After this I was able to install the package correctly or better I was able to upgrade 3.4.2 to 3.4.2_1.
Hi! I've reverted the change for now. The change is most likely due to the handling of gpg.conf, which is installed to silence the warning about "insecure memory", but I don't have time to investigate this week, so the change is reverted until I can have a look.
Thanks, that fixed it.