Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
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 18:03:13 +0200	[thread overview]
Message-ID: <2181287.8UlWShMbI3@sagittea> (raw)
In-Reply-To: <20160903063033.788551028C6@stock.ovh.net>

On Saturday 03 September 2016 08:30:33 Thomas Petazzoni wrote:
[...]
> mips64el |              util-linux-2.28.1 | NOK |
> http://autobuild.buildroot.net/results/e45931629ee3f5dc45de6940a2c0983435f77e00 
>      sh4 |              util-linux-2.28.1 | NOK |
> http://autobuild.buildroot.net/results/b3649dedd048515844675cd48b84bab74eb897f8 
>   x86_64 |              util-linux-2.28.1 | NOK |
> http://autobuild.buildroot.net/results/26b3a4de1fb8b366727299ff5de7d59b3e521c23

wget do not accept certificate from cdn.kernel.org. It seems to be
related to :
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=409938

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

Any opinion?

BR,

-- 
J?r?me Pouiller, Sysmic
Embedded Linux specialist
http://www.sysmic.fr

  reply	other threads:[~2016-09-03 16:03 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 [this message]
2016-09-03 18:10   ` Carlos Santos
2016-09-03 18:36   ` Thomas Petazzoni
2016-09-03 18:59     ` Jérôme Pouiller
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=2181287.8UlWShMbI3@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox