Changes between Version 27 and Version 28 of OpenvpnSoftwareRepos
- Timestamp:
- 10/25/16 11:26:50 (7 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
OpenvpnSoftwareRepos
v27 v28 5 5 Latest OpenVPN releases are also available in the OpenVPN project's apt repositories. This allow you to use more up-to-date version of OpenVPN than what's typically available in your distribution's repositories. Please note that all commands listed below have to be run as root, e.g. using ''sudo'' or ''su''. 6 6 7 Stable releases built from official releases are only available for Debian and Ubuntu. This is so for two reasons:7 Pre-built Linux binaries are only available for Debian and Ubuntu. This is so for two reasons: 8 8 9 9 * Official Debian and Ubuntu repositories tend to have fairly old OpenVPN versions available … … 12 12 All packages are available in ''i386'' and ''amd64/x86_64'' flavours. Even if a package is built on a particular OS, it does not mean it won't work on older and/or newer versions of the same distro, or even on a different operating system. If you encountered any issues with the package, please file a new [wiki:TesterDocumentation#Reportingbugs bug report]. 13 13 14 = Adding swupdate.openvpn.net apt repository=14 = Using OpenVPN apt repositories = 15 15 16 16 We maintain several OpenVPN (OSS) software repositories. To setup the repositories you need to change to the root user. Typically this is done using ''sudo'': … … 26 26 }}} 27 27 28 Next you need to create a sources.list fragment (as root) so that apt can find the new OpenVPN packages :28 Next you need to create a sources.list fragment (as root) so that apt can find the new OpenVPN packages. One way to do it is this: 29 29 30 30 {{{ 31 $ echo "deb http:// swupdate.openvpn.net/apt <osrelease> main" > /etc/apt/sources.list.d/swupdate.openvpn.net.list31 $ echo "deb http://build.openvpn.net/debian/openvpn/<version> <osrelease> main" > /etc/apt/sources.list.d/openvpn-aptrepo.list 32 32 }}} 33 33 34 Where <osrelease> depends your distribution:34 Where '''<version>''' can be one of 35 35 36 * ''wheezy'' (Debian 7.x) 37 * ''jessie'' (Debian 8.x) 38 * ''precise'' (Ubuntu 12.04) 39 * ''trusty'' (Ubuntu 14.04) 40 * ''xenial'' (Ubuntu 16.04) 36 1. '''stable''': stable releases only - no alphas, betas or RCs 37 1. '''testing''': latest releases, including alphas/betas/RCs 38 1. '''release/2.3''': OpenvPN 2.3 releases 39 1. '''release/2.4''': OpenVPN 2.4 releases, including alphas/betas/RCs 41 40 42 For example: 41 and '''<osrelease>''' depends your distribution: 42 43 * '''wheezy''' (Debian 7.x) 44 * '''jessie''' (Debian 8.x) 45 * '''precise''' (Ubuntu 12.04) 46 * '''trusty''' (Ubuntu 14.04) 47 * '''xenial''' (Ubuntu 16.04) 48 49 Examples: 43 50 44 51 {{{ 45 $ echo "deb http://swupdate.openvpn.net/apt wheezy main" > /etc/apt/sources.list.d/swupdate.openvpn.net.list 52 $ echo "deb http://build.openvpn.net/debian/openvpn/testing jessie main" > /etc/apt/sources.list.d/openvpn-aptrepo.list 53 $ echo "deb http://build.openvpn.net/debian/openvpn/release/2.3 wheezy main" > /etc/apt/sources.list.d/openvpn-aptrepo.list 46 54 }}} 47 55 … … 58 66 = Notes on expired keys = 59 67 60 The original apt signing key expired on 4th Aug 2014, resulting in apt complaintswhen refreshing the package cache (e.g. ''apt-get update''). To fix this remove the expired key from apt keychain:68 If the apt signing key expires, apt will complain when refreshing the package cache (e.g. ''apt-get update''). To fix this remove the expired key from apt keychain: 61 69 62 70 {{{ … … 76 84 --- snip --- 77 85 }}} 78 79 = Notes on old apt/yum repositories =80 81 The current incarnation of OpenVPN apt repositories is the third one. The first repositories were hosted on ''build.openvpn.net'' and the second ones on ''repos.openvpn.net'', a now discontinued server. The apt lines for the latter still work, but new OpenVPN releases (2.3.3 and later) will only be added to current ''swupdate.openvpn.net'' repos. Unfortunately due to the complete restructuring of the apt repository structure it is not possible to cleanly migrate from the ''repos.openvpn.net''-based configuration to the ''swupdate.openvpn.net'' configuration.