Unable to update Expedition "expedition-updates/ Release' does not have a Release file"

cancel
Showing results for 
Search instead for 
Did you mean: 

Unable to update Expedition "expedition-updates/ Release' does not have a Release file"

L1 Bithead

Currently have expedition 1.1.46.1 installed and running.

on "sudo apt-get update" I receive the message below.

 

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

N: Data from such a repository can't be authenticated and is therefore potentially dangerous to use.

 

I was unable to find any previous threads concerning this issue.

1 ACCEPTED SOLUTION

Accepted Solutions

L1 Bithead

Editing the repo list at /etc/apt/sources.list.d/ex-repo.list to include

deb [trusted=yes] https://conversionupdates.paloaltonetworks.com/ expedition-updates/

 

Prevents the warnings from appearing in the future.

 

View solution in original post

13 REPLIES 13

L5 Sessionator

This is a normal message due to the settings of our repository.

 

Continue ahead installing the updates.

This is not a solution. I have concerns on running Palo Alto software in my network considering the "push ahead" attitude when confronted with security concerns. Why has this software not been signed? Is it current PA policy to produce applications for enterprise use with such lenient security?

Hi,

 

We understand your concerns. This is not a product, but a tool offered for free to use and download, and not strictly required to run Palo Alto Networks products.

While we do not have the repository signed, the deb packages themselves are actually signed.

We have plans to provide certified repository listing as well, but it is not yet deployed and we have certain points with higher priority we want to get covered first.

L1 Bithead

Editing the repo list at /etc/apt/sources.list.d/ex-repo.list to include

deb [trusted=yes] https://conversionupdates.paloaltonetworks.com/ expedition-updates/

 

Prevents the warnings from appearing in the future.

 

Still an issue nine months (really years) later, though the work-around (not a solution) let's it continue, this violates most corporate policies of using signed repositories for updates. This has been requested for years, any chance we'll ever get the repo signed?

I have upated the ex-repo.list file as recommended, but I still see expedition-beta is already the newest version (1.1.104)

 

expedition@Expedition:~$ sudo apt-get install expedition-beta
Reading package lists... Done
Building dependency tree
Reading state information... Done
expedition-beta is already the newest version (1.1.104).
0 upgraded, 0 newly installed, 0 to remove and 117 not upgraded.
expedition@Expedition:~$ deb [trusted=yes] https://conversionupdates.paloaltonetworks.com/ expedition-updates/

 

Also, when I run the sudo apt-get update command, I see this error at the bottom of the output:

 

E: Failed to fetch https://conversionupdates.paloaltonetworks.com/expedition-updates/Packages Could not open file /var/lib/apt/lists/partial/conversionupdates.paloaltonetworks.com_expedition-updates_Packages.gz - open (13: Permission denied)

 

Any idea on how to get around this?

 

Thanks,

Blake

This is because the "sudo apt-get update" may not have updated.

I'm sorry, but you lost me there.  What do you mean sudo apt-get update may not have updated?

The expedition server has access to the internet, and I don't see any denied traffic for app-id apt-get.

 

Here's what I see when I do 'sudo apt-get update' and sudo apt-get install expedition-beta'

 

Err:30 http://ppa.launchpad.net/jonathonf/python-3.6/ubuntu xenial/main amd64 Packages
403 Forbidden [IP: 91.189.95.85 80]
Ign:31 http://ppa.launchpad.net/jonathonf/python-3.6/ubuntu xenial/main i386 Packages
Ign:32 http://ppa.launchpad.net/jonathonf/python-3.6/ubuntu xenial/main Translation-en
Reading package lists... Done
W: The repository 'http://www.rabbitmq.com/debian testing Release' does not have a Release file.
N: Data from such a repository can't be authenticated and is therefore potentially dangerous to use.
N: See apt-secure(8) manpage for repository creation and user configuration details.
W: The repository 'http://ppa.launchpad.net/jonathonf/python-3.6/ubuntu xenial Release' does not have a Release file.
N: Data from such a repository can't be authenticated and is therefore potentially dangerous to use.
N: See apt-secure(8) manpage for repository creation and user configuration details.
E: Failed to fetch https://www.rabbitmq.com/debian/dists/testing/main/binary-amd64/Packages 404 OK
E: Failed to fetch https://conversionupdates.paloaltonetworks.com/expedition-updates/Packages Could not open file /var/lib/apt/lists/partial/conversionupdates.paloaltonetworks.com_expedition-updates_Packages.gz - open (13: Permission denied)
E: Failed to fetch http://ppa.launchpad.net/jonathonf/python-3.6/ubuntu/dists/xenial/main/binary-amd64/Packages 403 Forbidden [IP: 91.189.95.85 80]
E: Some index files failed to download. They have been ignored, or old ones used instead.
expedition@Expedition:~$ sudo apt-get install expedition-beta
Reading package lists... Done
Building dependency tree
Reading state information... Done
expedition-beta is already the newest version (1.1.104).
0 upgraded, 0 newly installed, 0 to remove and 73 not upgraded.
expedition@Expedition:~$

Hello @Blake_Wofford 

 

Please refer to this post to resolve it then try to pull the update again and it should work.

 

https://live.paloaltonetworks.com/t5/expedition-discussions/unable-to-update-expedition-quot-expedit...

Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!