OpenVPN Ubuntu packages unsigned?

[greenpaint]

I'm receiving this error when updating:

Code: Select all

localhost sources.list.d [0]# apt-get -qq update
W: Failed to fetch http://swupdate.openvpn.net/apt/dists/trusty/Release  No Hash entry in Release file /var/lib/apt/lists/swupdate.openvpn.net_apt_dists_trusty_Release, which is considered strong enough for security purposes
E: Some index files failed to download. They have been ignored, or old ones used instead.

The repo for Trusty appears to contain the only release of OpenVPN 2.3.8 anywhere that's been packaged for Ubuntu; the Debian and Ubuntu teams themselves have stuck with 2.3.7 for some reason.

Is this still maintained, or would I be better off using the Ubuntu packages for 2.3.7?

[gmaydude]

I'm having the same error with Debian jessie. This started occurring after upgrading to:
apt (1.1~exp9) experimental; urgency=medium

A new algorithm for pinning has been implemented, it now assigns a
pin priority to a version instead of assigning a pin to a package.

This might break existing corner cases of pinning, if they use multiple
pins involving the same package name or patterns matching the same
package name, but should overall lead to pinning that actually works
as intended and documented.

-- Julian Andres Klode <jak@debian.org> Mon, 17 Aug 2015 14:45:17 +0200

W: Failed to fetch http://swupdate.openvpn.net/apt/dists/jessie/Release No Hash entry in Release file /var/lib/apt/lists/swupdate.openvpn.net_apt_dists_jessie_Release, which is considered strong enough for security purposes
E: Some index files failed to download. They have been ignored, or old ones used instead.

I deleted the /var/lib/apt/lists/swupdate.openvpn.net_apt_dists_jessie_Release file and ran apt-get update and still have the same error.

[samuli]

Hi,

This problem has been reported earlier with regards to latest Ubuntu alpha release. The problem is that our apt repository management tool, freight, is not compatible with latest changes in apt. I will upgrade or patch freight early next or so.

--
Samuli Seppänen
Community Manager
OpenVPN Technologies, Inc

irc freenode net: mattock

[samuli]

There are actually two different problems related to freight and apt 1.1+:

• https://github.com/rcrowley/freight/issues/65
• https://github.com/rcrowley/freight/issues/66

It will take a bit more time to fix this. If nothing happens at the freight end soon, I'll have to reproduce and fix this myself.