From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] wget download: 'scheme missing' results in empty output file
Date: Sun, 3 Jul 2016 11:54:28 +0200 [thread overview]
Message-ID: <20160703115428.24dad374@free-electrons.com> (raw)
In-Reply-To: <CAAXf6LXVweNYNvHNZG9bvYu9KVeAa9L6=qPOwRsmsx8DhVGTJQ@mail.gmail.com>
Hello,
On Thu, 25 Feb 2016 14:19:56 +0100, Thomas De Schampheleire wrote:
> Hi Yann, all,
>
> When a package does not (by error) define FOO_SITE, and the source
> archive is not already present, the wget download helper will be
> invoked with as URL /foo-xxx.tar.gz. wget reports 'Scheme missing' and
> bails out, but _returns with a successful error code (0)_.
>
> As a result, the download helper happily continues with hash checking
> and finally with the atomic mv of the temporary download file (which
> has been created but is still empty) to the final output location.
>
> Because as far as the download helper is concerned, everything went
> successfully, also the build continues (but obviously fails further
> on).
>
> While I think wget should not return 0 on such a problem, I think we
> should try and prevent such problems. One way is to expect the
> downloaded file size to be greater than 0. If that requirement is not
> met, the download helper should bail out.
>
> A patch like the below fixes the problem:
Instead of this, I just submitted a patch that verifies that SITE is
not empty if SOURCE is not empty. See
https://patchwork.ozlabs.org/patch/643725/. Consequently, I've marked
your patch as Superseded in patchwork.
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2016-07-03 9:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-25 13:19 [Buildroot] wget download: 'scheme missing' results in empty output file Thomas De Schampheleire
2016-02-25 15:40 ` Peter Korsgaard
2016-02-25 16:05 ` Thomas De Schampheleire
2016-02-25 16:21 ` Peter Korsgaard
2016-02-25 16:07 ` Thomas Petazzoni
2016-02-25 16:13 ` Thomas De Schampheleire
2016-02-25 16:34 ` Peter Korsgaard
2016-02-25 17:01 ` Thomas Petazzoni
2016-02-25 20:32 ` Yann E. MORIN
2016-03-18 9:43 ` Thomas De Schampheleire
2016-07-03 9:54 ` Thomas Petazzoni [this message]
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=20160703115428.24dad374@free-electrons.com \
--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