From: "Jérôme Pouiller" <jezz@sysmic.org>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2016-09-02
Date: Sat, 03 Sep 2016 20:59:08 +0200 [thread overview]
Message-ID: <1496256.AqCB2eOqyL@sagittea> (raw)
In-Reply-To: <20160903203613.2a7f0a32@free-electrons.com>
On Saturday 03 September 2016 20:36:13 Thomas Petazzoni wrote:
> Hello,
>
> On Sat, 03 Sep 2016 18:03:13 +0200, J?r?me Pouiller wrote:
> > wget >= 1.13-1 is necessary to fix problem. I see three solutions:
> > 1. Revert de76cb7da734dde2204a7ea9ff60e24cbe857ddb ("Use CDN
> >
> > kernel.org mirror")
> >
> > 2. Use http instead if https
> > 3. Check wget version in dependencies.sh
>
> 4. The problem is already solved, because the util-linux-2.28.1.tar.xz
> tarball is now on http://sources.buildroot.net/, and Buildroot
> automatically falls back to this address. Therefore, the build
> failure will no longer occur.
It means this error will occurs each time a package using KERNEL_MIRROR
will be upgraded? Do autobuilder owners could update their wget version?
> However, we could discuss whether it really makes sense to use
> https:// as the main download location when all downloads anyway fall
> back to downloading from sources.buildroot.net over http://.
sources.buildroot.net should provide an https access?
BR,
--
J?r?me Pouiller, Sysmic
Embedded Linux specialist
http://www.sysmic.fr
next prev parent reply other threads:[~2016-09-03 18:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-03 6:30 [Buildroot] [autobuild.buildroot.net] Build results for 2016-09-02 Thomas Petazzoni
2016-09-03 16:03 ` Jérôme Pouiller
2016-09-03 18:10 ` Carlos Santos
2016-09-03 18:36 ` Thomas Petazzoni
2016-09-03 18:59 ` Jérôme Pouiller [this message]
2016-09-03 21:23 ` Thomas Petazzoni
2016-09-05 8:05 ` Peter Korsgaard
2016-09-05 8:20 ` Jérôme Pouiller
2016-09-05 9:30 ` Yann E. MORIN
2016-09-05 16:09 ` Peter Korsgaard
2016-09-05 16:22 ` Jérôme Pouiller
2016-09-05 6:40 ` Peter Korsgaard
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=1496256.AqCB2eOqyL@sagittea \
--to=jezz@sysmic.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.