From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 0/7 v4] support/download: be more aggressive on missing hashes (branch yem/dl-hash-2)
Date: Thu, 02 Apr 2015 23:34:41 +0200 [thread overview]
Message-ID: <551DB5F1.60700@mind.be> (raw)
In-Reply-To: <20150401205235.GC4235@free.fr>
On 01/04/15 22:52, Yann E. MORIN wrote:
> Thomas, All,
>
> On 2015-04-01 22:08 +0200, Thomas Petazzoni spake thusly:
>> On Wed, 1 Apr 2015 00:15:03 +0200, Yann E. MORIN wrote:
>>> This series makes hashes mandatory when a .hash file exists.
> [--SNIP--]
>> I applied this and was going to push it, but I believe there's still a
>> problem.
>>
>> If I change strace.hash so that there is no hash matching the tarball
>> name of strace, then I get two times the error:
>>
>> $ make strace-extract
>> ERROR: No hash found for strace-4.10.tar.xz
>> ERROR: No hash found for strace-4.10.tar.xz
>> package/pkg-generic.mk:73: recipe for target '/home/thomas/projets/buildroot/output/build/strace-4.10/.stamp_downloaded' failed
>>
>> I haven't looked too deeply, but I believe it's because check-hash
>> returns 3, so dl-wrapper exits with error code 1, which means that the
>> pkg-download.mk logic concludes that the download from the upstream
>> location has failed, so it retries with sources.buildroot.net, and the
>> same thing happens.
>>
>> Is this expected?
>
> That's at least the result I expect, yes.
>
> I know this might look weird, indeed. However, I did not find a
> simple
> way to avoid this.
I think this weird behaviour is acceptable (for now). It is indeed hard to
avoid, and anyway this is not something that a normal user would ever encounter.
In a perfect world the entire download logic would move to a script (which
admittedly would get a sh*tload of arguments). Then it would be much simpler to
exit properly.
Regards,
Arnout
[snip]
--
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:[~2015-04-02 21:34 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-31 22:15 [Buildroot] [PATCH 0/7 v4] support/download: be more aggressive on missing hashes (branch yem/dl-hash-2) Yann E. MORIN
2015-03-31 22:15 ` [Buildroot] [PATCH 1/7 v4] support/download: make hash file optional Yann E. MORIN
2015-03-31 22:15 ` [Buildroot] [PATCH 2/7 v4] package infra: do not check hashes when downloading from a repository Yann E. MORIN
2015-04-02 21:38 ` Arnout Vandecappelle
2015-04-02 21:49 ` Yann E. MORIN
2015-04-02 21:57 ` Arnout Vandecappelle
2015-04-02 22:08 ` Yann E. MORIN
2015-03-31 22:15 ` [Buildroot] [PATCH 3/7 v4] support/download: add explicit no-hash support Yann E. MORIN
2015-03-31 22:15 ` [Buildroot] [PATCH 4/7 v4] support/download: return different exit codes for different failures Yann E. MORIN
2015-04-02 21:41 ` Arnout Vandecappelle
2015-03-31 22:15 ` [Buildroot] [PATCH 5/7 v4] support/download: properly catch missing hashes Yann E. MORIN
2015-03-31 22:15 ` [Buildroot] [PATCH 6/7 v4] support/download: always fail when there's no hash Yann E. MORIN
2015-03-31 22:15 ` [Buildroot] [PATCH 7/7 v4] support/download: warn when there's no .hash file Yann E. MORIN
2015-04-01 20:08 ` [Buildroot] [PATCH 0/7 v4] support/download: be more aggressive on missing hashes (branch yem/dl-hash-2) Thomas Petazzoni
2015-04-01 20:52 ` Yann E. MORIN
2015-04-02 21:34 ` Arnout Vandecappelle [this message]
2015-04-02 21:53 ` Arnout Vandecappelle
2015-04-03 12:11 ` Thomas Petazzoni
2015-04-03 12:13 ` Yann E. MORIN
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=551DB5F1.60700@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