Changes between Version 27 and Version 28 of OpenvpnSoftwareRepos


Ignore:
Timestamp:
10/25/16 11:26:50 (7 years ago)
Author:
Samuli Seppänen
Comment:

Document the new apt repositories

Legend:

Unmodified
Added
Removed
Modified
  • OpenvpnSoftwareRepos

    v27 v28  
    55Latest 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''.
    66
    7 Stable releases built from official releases are only available for Debian and Ubuntu. This is so for two reasons:
     7Pre-built Linux binaries are only available for Debian and Ubuntu. This is so for two reasons:
    88
    99 * Official Debian and Ubuntu repositories tend to have fairly old OpenVPN versions available
     
    1212All 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].
    1313
    14 = Adding swupdate.openvpn.net apt repository =
     14= Using OpenVPN apt repositories =
    1515
    1616We maintain several OpenVPN (OSS) software repositories. To setup the repositories you need to change to the root user. Typically this is done using ''sudo'':
     
    2626}}}
    2727
    28 Next you need to create a sources.list fragment (as root) so that apt can find the new OpenVPN packages:
     28Next 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:
    2929
    3030{{{
    31 $ echo "deb http://swupdate.openvpn.net/apt <osrelease> main" > /etc/apt/sources.list.d/swupdate.openvpn.net.list
     31$ echo "deb http://build.openvpn.net/debian/openvpn/<version> <osrelease> main" > /etc/apt/sources.list.d/openvpn-aptrepo.list
    3232}}}
    3333
    34 Where <osrelease> depends your distribution:
     34Where '''<version>''' can be one of
    3535
    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
    4140
    42 For example:
     41and '''<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
     49Examples:
    4350
    4451{{{
    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
    4654}}}
    4755
     
    5866= Notes on expired keys =
    5967
    60 The original apt signing key expired on 4th Aug 2014, resulting in apt complaints when refreshing the package cache (e.g. ''apt-get update''). To fix this remove the expired key from apt keychain:
     68If 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:
    6169
    6270{{{
     
    7684--- snip ---
    7785}}}
    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.