Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Egbert Verhage <egbert@eggiecode.org>
To: wireguard@lists.zx2c4.com
Subject: Re: wg binary in armhf deb from ppa missing
Date: Sun, 19 Feb 2017 15:51:42 +0100	[thread overview]
Message-ID: <37c21d07-0153-7fa2-8fe3-c852704e53b9@eggiecode.org> (raw)
In-Reply-To: <EF6AB0BF-E341-41C1-8744-7CA8A5A778D0@dd19.de>

Hey Alex,

Ow, I never tested the package on armhf. I will give test it tomorrow on
my own Banana Pi 2 and Raspberry pi 2.

If you are running the image of lemaker on your banana pi, maybe try
first to build the package from the git repo.

Greetz,
Egbert


On 2017-02-19 02:14, Alexander Morlang wrote:
> Hi,
> used the launchpad ppa in xenial on armhf (Banana Pro). 
> The wireguard-tools packet installed only /usr/share/doc
>
> Is this a known problem?
>
> I downloaded the
> https://launchpad.net/~wireguard/+archive/ubuntu/wireguard/+files/wireguard-tools_0.0.20170214-wg1~xenial_armhf.deb
> and hat a look with dpkg -c <file>, getting the same result of no binary in the packet.
>
> regards, Alex
> _______________________________________________
> WireGuard mailing list
> WireGuard@lists.zx2c4.com
> https://lists.zx2c4.com/mailman/listinfo/wireguard

  reply	other threads:[~2017-02-19 14:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-19  1:14 Alexander Morlang
2017-02-19 14:51 ` Egbert Verhage [this message]
2017-02-19 16:27   ` Egbert Verhage
2017-02-19 16:29   ` Alexander Morlang
2017-02-19 18:21     ` wg binary in armhf deb from ppa missing; armbian with Allwinner A20 chip modprobe wg not working Egbert Verhage
     [not found]       ` <CAHmME9ossQJ3U54yOmY98dcdG239xm6KeHQt+n8zb6R0x4yUZA@mail.gmail.com>
2017-02-19 19:02         ` Jason A. Donenfeld

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=37c21d07-0153-7fa2-8fe3-c852704e53b9@eggiecode.org \
    --to=egbert@eggiecode.org \
    --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).