From: Egbert Verhage <egbert@eggiecode.org>
To: Alexander Morlang <alx@dd19.de>
Cc: wireguard@lists.zx2c4.com
Subject: Re: wg binary in armhf deb from ppa missing
Date: Sun, 19 Feb 2017 17:27:33 +0100 [thread overview]
Message-ID: <e77f62c0-04de-f45d-6a86-15e351c98551@eggiecode.org> (raw)
In-Reply-To: <37c21d07-0153-7fa2-8fe3-c852704e53b9@eggiecode.org>
[-- Attachment #1.1: Type: text/plain, Size: 1844 bytes --]
Hey Alex,
This is strange. Just builded the package on my PI and it is working as
intended.
(https://eggiecode.org/wireguard-tools_0.0.20170214-wg1~xenial_armhf.deb
<https://eggiecode.org/wireguard-tools_0.0.20170214-wg1%7Exenial_armhf.deb>)
The PPA build systems screwed the tools package up, looks like it is not
running `make install` to the package.
See the build log differance in the ppa of armhf and amd64.
Greetz,
Egbert
armhf:
https://launchpadlibrarian.net/306379568/buildlog_ubuntu-yakkety-armhf.wireguard_0.0.20170214-wg1~yakkety_BUILDING.txt.gz
amd64:
https://launchpadlibrarian.net/306379566/buildlog_ubuntu-yakkety-amd64.wireguard_0.0.20170214-wg1~yakkety_BUILDING.txt.gz
On 2017-02-19 15:51, Egbert Verhage wrote:
> 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
> _______________________________________________
> WireGuard mailing list
> WireGuard@lists.zx2c4.com
> https://lists.zx2c4.com/mailman/listinfo/wireguard
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 963 bytes --]
next prev parent reply other threads:[~2017-02-19 16:27 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
2017-02-19 16:27 ` Egbert Verhage [this message]
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=e77f62c0-04de-f45d-6a86-15e351c98551@eggiecode.org \
--to=egbert@eggiecode.org \
--cc=alx@dd19.de \
--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).