I accept this solution, but I'm not enthusiastic about it. I don't recall encountering the apt update error when I previously performed an upgrade. You are instructing me to "go ahead anyway," despite bad signs about whether the process is going well. That isn't good security advice. The fact that the repo gives errors, and that the package itself is not signed, do not give me confidence in how this software is being produced. It is not professional-grade work, and PAN should do better. (That statement stands on its own, but consider the 2017 CCleaner malware incident if you need more convincing.) Nevertheless, you are correct that proceeding with the apt upgrade step despite the repo error does result in Expedition getting upgraded to version 1.1.1. Thanks for your help.
... View more