All of lore.kernel.org
 help / color / mirror / Atom feed
From: Egbert Verhage <egbert@eggiecode.org>
To: Steve Pagan <spagan@instartlogic.com>, wireguard@lists.zx2c4.com
Subject: Re: Repo broken?
Date: Fri, 26 May 2017 22:54:20 +0200	[thread overview]
Message-ID: <1495832060.1086.1.camel@eggiecode.org> (raw)
In-Reply-To: <CAK-i-m_Bv92mtdbPXZrqmC5pqiVkMrP=DsY8Hc69BZ_0McRQZA@mail.gmail.com>

Hey Steve,

That is because in the beging of the ppa repo we only had support for
kernel >4.1.

On snapshot: 0.0.20170409 we got support for 3.16, 3.14, 3.12, 3.10.
And precise has kernel 3.2 (OLD!) and since April 28, 2017 precise is
eol.

Best way to run wireguard on ubuntu is run xenial or a higher release.

Greetz,
Egbert


On Fri, 2017-05-26 at 10:26 -0700, Steve Pagan wrote:
> I cannot download the required packages to my system. I get a 404
> error:
> 
> W: Failed to fetch http://ppa.launchpad.net/wireguard/wireguard/ubunt
> u/dists/precise/main/source/Sources  404  Not Found
> 
> W: Failed to fetch http://ppa.launchpad.net/wireguard/wireguard/ubunt
> u/dists/precise/main/binary-amd64/Packages  404  Not Found
> 
> W: Failed to fetch http://ppa.launchpad.net/wireguard/wireguard/ubunt
> u/dists/precise/main/binary-i386/Packages  404  Not Found
> 
>  
>  World's First Endpoint-Aware Application Delivery Solution
> Steve Pagan 
> Network Engineer - Operations
> 
> Phone: 650-919-8856 | Email: spagan@instartlogic.com 
> Instart Logic | 450 Lambert Ave, Palo Alto, CA 94306
> | instartlogic.com 
> _______________________________________________
> WireGuard mailing list
> WireGuard@lists.zx2c4.com
> https://lists.zx2c4.com/mailman/listinfo/wireguard

  parent reply	other threads:[~2017-05-26 20:42 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-26 17:26 Repo broken? Steve Pagan
2017-05-26 17:32 ` Bzzzz
2017-05-26 17:39   ` Steve Pagan
2017-05-26 17:45 ` Jonathon Fernyhough
2017-05-26 17:52   ` Steve Pagan
2017-05-26 18:00     ` Bzzzz
2017-05-26 20:54 ` Egbert Verhage [this message]
2017-05-26 23:33   ` Jonathon Fernyhough

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1495832060.1086.1.camel@eggiecode.org \
    --to=egbert@eggiecode.org \
    --cc=spagan@instartlogic.com \
    --cc=wireguard@lists.zx2c4.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.