From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2017-06-23
Date: Sat, 24 Jun 2017 22:38:52 +0200 [thread overview]
Message-ID: <20170624223852.7812d38d@windsurf.home> (raw)
In-Reply-To: <20170624195411.37qp6b5ocvenrjeo@tarshish>
Hello,
On Sat, 24 Jun 2017 22:54:11 +0300, Baruch Siach wrote:
> On Sat, Jun 24, 2017 at 08:30:43AM +0200, Thomas Petazzoni wrote:
> > aarch64 | openvpn-2.4.3 | NOK | http://autobuild.buildroot.net/results/937c2c1e025bb16ca6fc26bc025ca728ad92bd3b |
> > x86_64 | openvpn-2.4.3 | NOK | http://autobuild.buildroot.net/results/d397964e0a9b97fcc887143cdeaa02137e92469a |
> > xtensa | openvpn-2.4.3 | NOK | http://autobuild.buildroot.net/results/dccea3d71f2433f45eca4403343a15d01dda5be7 |
> > aarch64 | openvpn-2.4.3 | NOK | http://autobuild.buildroot.net/results/af9accf066801b61bc05f0deef0ea6cdf36dabed |
> > m68k | openvpn-2.4.3 | NOK | http://autobuild.buildroot.net/results/a114fef820ed6e25603ded8594e6930f952cdfa2 |
> > powerpc | openvpn-2.4.3 | NOK | http://autobuild.buildroot.net/results/e25e8b031a944320c6ab5260220910b03820bfda |
> > nios2 | openvpn-2.4.3 | NOK | http://autobuild.buildroot.net/results/ee77acba11239511009bd98255599c9ecc043f6c |
> > mipsel | openvpn-2.4.3 | NOK | http://autobuild.buildroot.net/results/059e916b409e8aac42f565c9eba29bd8fad9cadf |
>
> >>> openvpn 2.4.3 Downloading
> converted 'http://swupdate.openvpn.net/community/releases/openvpn-2.4.3.tar.xz' (ANSI_X3.4-1968) -> 'http://swupdate.openvpn.net/community/releases/openvpn-2.4.3.tar.xz' (UTF-8)
> --2017-06-23 22:00:10-- http://swupdate.openvpn.net/community/releases/openvpn-2.4.3.tar.xz
>
> [...]
>
> 2017-06-23 22:00:10 (7.26 MB/s) - '/home/buildroot/build/instance-0/output/build/.openvpn-2.4.3.tar.xz.AZpKge/output' saved [929028/929028]
>
> ERROR: openvpn-2.4.3.tar.xz has wrong sha256 hash:
> ERROR: expected: 15e15fc97f189b52aee7c90ec8355aa77469c773125110b4c2f089abecde36fb
> ERROR: got : 7aa86167a5b8923e54e8795b814ed77288c793671f59fd830d9ab76d4b480571
> ERROR: Incomplete download, or man-in-the-middle (MITM) attack
>
> Not sure what is going on here. I have now tried again a fresh download, and
> also compared to the tarball I have in dl/. In both cases I get the expected
> hash. The tarball size here is 938440.
>
> Maybe different downloaders get different tarballs?
>
> What is the content of that tarball?
>
> Does it match the signature[1]?
Indeed, weird. According to
http://autobuild.buildroot.net/?reason=openvpn-2.4.3, this only happens
on Yann and Richard autobuilder instances. Yann, Richard, could you
manually try to download
http://swupdate.openvpn.net/community/releases/openvpn-2.4.3.tar.xz,
and see what its sha256 hash is?
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-06-24 20:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-24 6:30 [Buildroot] [autobuild.buildroot.net] Build results for 2017-06-23 Thomas Petazzoni
2017-06-24 19:54 ` Baruch Siach
2017-06-24 20:38 ` Thomas Petazzoni [this message]
[not found] ` <20170624224502.GA8771@shattrath>
2017-06-25 3:13 ` Baruch Siach
2017-06-25 9:07 ` Yann E. MORIN
2017-06-25 9:25 ` Yann E. MORIN
2017-06-25 9:54 ` Yann E. MORIN
2017-06-25 7:09 ` Bernd Kuhls
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=20170624223852.7812d38d@windsurf.home \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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