privoxy-pki-bundle: Image error: /opt/local/etc/privoxy/CA/trustedCAs.pem already exists and does not belong to a registered port

[ryandesign (Ryan Carsten Schmidt)]

On most of the buildbot machines this error occurs when trying to activate privoxy-pki-bundle:

​https://build.macports.org/builders/ports-12_arm64-builder/builds/56031/steps/install-port/logs/stdio

Error: Failed to activate privoxy-pki-bundle: Image error: /opt/local/etc/privoxy/CA/trustedCAs.pem already exists and does not belong to a registered port.  Unable to activate port privoxy-pki-bundle. Use 'port -f activate privoxy-pki-bundle' to force the activation.

On the servers, this file was created October 19, 2021. Looks like that was as a result of [17dbffd4a4878130afd546886e3240bb3bd862be/macports-ports] adding a post-activate block to the privoxy port to copy trustedCAs.pem into the prefix, bypassing the destroot.

This code was subsequently removed from the privoxy port and now the privoxy-pki-bundle subport wants to install that file, but can't since the unregistered file still exists, both on buildbot system and on the systems of any user who had installed the port before.

A pre-activate block should probably be added to the privoxy-pki-bundle subport that deletes this file; the block should stay in the port for a year or so to give people a chance to upgrade and receive the fix.

[essandess (Steve Smith)]

Please see ​https://github.com/macports/macports-ports/pull/15212.

[essandess (Steve Smith)]

In e77667f920242520c46e4bb148c3813d2f0734d9/macports-ports (master):

privoxy: Bugfix presence of existing trustedCAs.pem file

• Fixes: #65367