From: Egbert Verhage <egbert@eggiecode.org>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: wireguard-tools Ubuntu package missing the binaries
Date: Sun, 16 Apr 2017 18:04:10 +0200 [thread overview]
Message-ID: <1492358650.1445.11.camel@eggiecode.org> (raw)
In-Reply-To: <CAHmME9pc6jFnb5NMYt=yi+voWjsg4dS=NC+X1tY2qY4xbo1oVA@mail.gmail.com>
To clarify my message.
Going to fix/test the package on arm and i386 with hda.
Then will update my PI to ubuntu 17.04 to add that to the package.
Greetz,
Egbert
On Sun, 2017-04-16 at 17:50 +0200, Jason A. Donenfeld wrote:
> I did not comprehend your message. Is the problem fixed and are
> packages that actually work available now on Launchpad?
>
On Sun, 2017-04-16 at 17:47 +0200, Egbert Verhage wrote:
>
> This problem got previously with my RaspPi. That tools binaries build
> are not in de build of armv6 and think that is the same with i386.
>
> This was a old item in the mailing list about arm packages in ubuntu
> repo: https://lists.zx2c4.com/pipermail/wireguard/2017-February/00105
> 0.
> html
> Coud not figer out what the problem was.
>
> And a great time to add ubuntu 17.04 (zesty) and test it on my pi.
>
> hda (cryptofuture) is testing it now on his own ppa, see here the
> github issue: https://github.com/EggieCode/wireguard-ppa/issues/13
> and
> the fix https://github.com/EggieCode/wireguard-ppa/pull/14
next prev parent reply other threads:[~2017-04-16 15:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-16 11:06 Ryan Riley
2017-04-16 11:24 ` Jonathon Fernyhough
2017-04-16 15:47 ` Egbert Verhage
2017-04-16 15:50 ` Jason A. Donenfeld
2017-04-16 16:04 ` Egbert Verhage [this message]
2017-04-16 17:50 ` wireguard-tools Ubuntu package missing the binaries; Fixed Egbert Verhage
2017-04-17 6:19 ` Ryan Riley
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=1492358650.1445.11.camel@eggiecode.org \
--to=egbert@eggiecode.org \
--cc=Jason@zx2c4.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).