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: Mon, 05 Sep 2016 18:22:04 +0200	[thread overview]
Message-ID: <4479898.zYZWECoz4p@sagittea> (raw)
In-Reply-To: <20160903232302.40ff0733@free-electrons.com>

On Saturday 03 September 2016 23:23:02 Thomas Petazzoni wrote:
> Hello,
> 
> On Sat, 03 Sep 2016 20:59:08 +0200, J?r?me Pouiller wrote:
> > > 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?
> 
> Sadly, yes.
> 
> > Do autobuilder owners could update their wget version?
> 
> Could be a solution. My autobuilder is intentionally running a very
> old system so that we catch such issues. Upgrading wget would solve
> this problem, but Buildroot users that must use old systems (which is
> sometimes the case in corporate environments) would still face the
> same issue. So keeping an old system for testing on our side is also
> a way of making sure that we face the same problems as those users,
> and can anticipate/fix them when possible.

I didn't check autobuilder code, but it should be possible to detect 
this case (old wget + SSL problem + 404 while checking mirror). We may 
associate this failure with a special package name? So developers know 
it should normally be ignored.


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

  parent reply	other threads:[~2016-09-05 16:22 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
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 [this message]
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=4479898.zYZWECoz4p@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