When the installer ends up getting to “Trusting FreePBX…Trusted” (as displayed in the ‘No improvement’ log provided above), the downloads that follow still receive “File Integrity failed”.
I understand that. If I manually retrieve and install the proper GPG key from pool.sks-keyservers.net BEFORE running the installer, there are NO problems. If I manually retrieve and install the proper GPG key from pool.sks-keyservers.net AFTER running the installer, all the existing problems are corrected. It certainly appears there is some kind of problem with your retrieval/installation of the GPG key when installing on Debian 9.
C’mon Andrew, you know what I meant. You also know that I’m fully aware that Framework, Core, etc. are part of the ‘bare minimum’.
Playing word games isn’t going to solve anything. If you don’t want to pursue this problem, I can’t force you.
I’ve put a bandaid on the problem by retrieving/installing the proper GPG key after Asterisk is installed and before the FreePBX installer is launched. If the key ever changes without the problem being fixed, a key refresh will obviously be necessary.
The way this works is that everything is done through the asterisk user with complex fopen commands and can be different on different systems. I will need a debian 9 system to login to so I will have to go spin one up.
I really can’t provide you with commands to run and check as the code in that area is particularly complex.
This will also be a problem for third party module distributors who have signed their own keys and then want to put modules onto your PIs using Debian 9 the modules will always show tampered.
My point is running refresh keys before freepbx is install means you are refreshing nothing. I have a feeling that the directories aren’t being created for gpg until you run those commands and they fail otherwise. Will have to keep dogging.