From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2014-04-10
Date: Fri, 18 Apr 2014 18:27:47 +0200 [thread overview]
Message-ID: <53515283.5060106@mind.be> (raw)
In-Reply-To: <87r4543r0z.fsf@dell.be.48ers.dk>
On 11/04/14 16:00, Peter Korsgaard wrote:
>>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:
>
> > Aah, exactly! Except that the download was not interrupt by doing a
> > Ctrl+C, and it's actually wget which retried the download. And:
>
> > 2014-04-08 04:27:12 (3.70 MB/s) - Connection closed at byte 1057288. Retrying.
>
> > The size at which the download was interrupted matches exactly my
> > findings.
>
> > Is it a bug in wget? Some option we forgot to pass to wget?
>
> Seems like a bug to me. I don't see how this could ever be valid
> behaviour.
Could also be a bug in the server: if it claims to support the Range:
option, then wget will try to use it. But if the server then returns the
start of the file instead of the request offset, you'll end up with this
corrupted file.
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
next prev parent reply other threads:[~2014-04-18 16:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-11 6:30 [Buildroot] [autobuild.buildroot.net] Build results for 2014-04-10 Thomas Petazzoni
2014-04-11 7:01 ` Peter Korsgaard
2014-04-11 7:30 ` Thomas Petazzoni
2014-04-11 8:04 ` Peter Korsgaard
2014-04-11 11:51 ` Mike Zick
2014-04-11 12:13 ` Thomas Petazzoni
2014-04-11 12:39 ` Baruch Siach
2014-04-11 12:59 ` Thomas Petazzoni
2014-04-11 14:00 ` Peter Korsgaard
2014-04-18 16:27 ` Arnout Vandecappelle [this message]
2014-04-19 12:11 ` Thomas Petazzoni
2014-04-19 14:17 ` Mike Zick
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=53515283.5060106@mind.be \
--to=arnout@mind.be \
--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