From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/4] package/mender-artifact: bump version to 3.4.0
Date: Tue, 11 Aug 2020 23:58:33 +0200 [thread overview]
Message-ID: <20200811235833.03115c8b@windsurf.home> (raw)
In-Reply-To: <20200715173707.584226-1-aduskett@gmail.com>
Hello,
+Matt since his autobuilders are causing issues.
+Christian for some more Go expertise.
On Wed, 15 Jul 2020 10:37:04 -0700
aduskett at gmail.com wrote:
> From: Adam Duskett <Aduskett@gmail.com>
>
> Update the following license file hashes due to copyright year changes:
> - vendor/github.com/mendersoftware/mendertesting/LICENSE
> - vendor/github.com/davecgh/go-spew/LICENSE
> - vendor/github.com/stretchr/testify/LICENSE
>
> Add hashes for the the following new files:
> - vendor/github.com/minio/sha256-simd/LICENSE
> - vendor/gopkg.in/yaml.v2/LICENSE
> - vendor/github.com/klauspost/compress/LICENSE
> - vendor/github.com/russross/blackfriday/v2/LICENSE.txt
> - vendor/github.com/klauspost/pgzip/LICENSE
> - vendor/github.com/cpuguy83/go-md2man/v2/LICENSE.md
> - vendor/github.com/shurcooL/sanitized_anchor_name/LICENSE
>
> Signed-off-by: Adam Duskett <Aduskett@gmail.com>
This is causing some significant amount of build failures in the
autobuilders:
http://autobuild.buildroot.net/?reason=host-mender%
It fails only on Matthew Weber autobuilders, which don't have a
"normal" access to Internet, and the build fails with errors such as:
go: github.com/davecgh/go-spew at v1.1.1: Get https://proxy.golang.org/github.com/davecgh/go-spew/@v/v1.1.1.mod: proxyconnect tcp: read tcp 192.168.6.146:34964->128.24.38.25:9091: read: connection reset by peer
go: github.com/davecgh/go-spew at v1.1.1: Get https://proxy.golang.org/github.com/davecgh/go-spew/@v/v1.1.1.mod: proxyconnect tcp: net/http: TLS handshake timeout
Can this be fixed somehow ?
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2020-08-11 21:58 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-15 17:37 [Buildroot] [PATCH 1/4] package/mender-artifact: bump version to 3.4.0 aduskett at gmail.com
2020-07-15 17:37 ` [Buildroot] [PATCH 2/4] package/mender: bump version to 2.3.0 aduskett at gmail.com
2020-07-15 17:37 ` [Buildroot] [PATCH 3/4] package/mender: set the default script version to 3 aduskett at gmail.com
2020-07-15 17:37 ` [Buildroot] [PATCH 4/4] package/mender: add support for update modules aduskett at gmail.com
2020-07-15 21:50 ` [Buildroot] [PATCH 1/4] package/mender-artifact: bump version to 3.4.0 Thomas Petazzoni
2020-07-17 12:51 ` Thomas Petazzoni
2020-08-06 10:57 ` Mirza Krak
2020-08-06 12:41 ` Mirza Krak
2020-08-11 21:58 ` Thomas Petazzoni [this message]
2020-08-12 2:26 ` Christian Stewart
2020-08-12 8:22 ` Thomas Petazzoni
2020-08-13 18:52 ` Adam Duskett
2020-08-13 19:39 ` Christian Stewart
2020-08-13 20:04 ` Adam Duskett
2020-08-13 20:20 ` Christian Stewart
2020-08-13 21:41 ` Christian Stewart
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=20200811235833.03115c8b@windsurf.home \
--to=thomas.petazzoni@bootlin.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