topic Re: Expedition won't update (404 error, "repository has no Release file") since upgrade to in Expedition Discussions

Expedition won't update (404 error, "repository has no Release file") since upgrade to 1.1

ChrisUrsich — Fri, 21 Dec 2018 21:55:00 GMT

I upgraded Expedition to version 1.1 with no problem, but since then, the APT package update has consistently reported:

Err:10 https://conversionupdates.paloaltonetworks.com expedition-updates/ Release
  404  Not Found

E: The repository 'https://conversionupdates.paloaltonetworks.com expedition-updates/ Release' does not have a Release file.

As you can see, the problem is a straightforward HTTP 404 error, as in the repo website is broken.

Re: Expedition won't update (404 error, "repository has no Release file") since upgrade to

alestevez — Sat, 22 Dec 2018 15:15:26 GMT

Hi, not true at all 🙂 That means only the Release file was not found (in purpose) but if now you continue with the next command

sudo apt-get install expedition-beta

You will see how upgrades, please let us know

Re: Expedition won't update (404 error, "repository has no Release file") since upgrade to

ChrisUrsich — Wed, 26 Dec 2018 16:32:26 GMT

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.