From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@openembedded.org
Subject: Re: checksums situation
Date: Thu, 26 Feb 2009 09:10:35 +0100 [thread overview]
Message-ID: <go5ipr$nvl$1@ger.gmane.org> (raw)
In-Reply-To: <go4f92$khh$2@ger.gmane.org>
On 25-02-09 23:04, Vitus Jensen wrote:
> If this leads you to abandon checksums alltogether: the current situation
> protects against corrupt downloads and otherwise undetected updates from
> upstream and I'm all for keeping such a protection.
I get reports pretty much every single week about someone asking "what
does 'checksum failed' mean" when their download is corrupt due to evil
proxies and bad disks. It's a lot easier and faster to debug than
seemingly random build failures.
regards,
Koen
next prev parent reply other threads:[~2009-02-26 8:14 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-13 16:28 checksums situation Marcin Juszkiewicz
2009-02-13 17:08 ` Otavio Salvador
2009-02-13 17:39 ` Ihar Hrachyshka
2009-02-13 18:37 ` Otavio Salvador
2009-02-13 19:35 ` Leon Woestenberg
2010-02-12 18:45 ` mike
2009-02-13 19:41 ` John Willis
2009-02-15 10:04 ` Phil Blundell
2009-02-15 18:32 ` Otavio Salvador
2009-02-13 17:09 ` Tom Rini
2009-02-13 17:28 ` Andrea Adami
2009-02-13 17:34 ` Andrea Adami
2009-02-13 18:02 ` Koen Kooi
2009-02-14 14:51 ` Yuri Bushmelev
2009-02-24 6:46 ` Tom Rini
2009-02-24 6:51 ` Tom Rini
2009-02-24 8:49 ` Marcin Juszkiewicz
2009-02-24 15:02 ` Tom Rini
2009-02-24 16:13 ` Michael 'Mickey' Lauer
2009-02-24 16:25 ` Angus Ainslie
2009-02-24 16:37 ` Tom Rini
2009-02-24 16:28 ` Philip Balister
2009-02-24 16:36 ` Tom Rini
2009-02-24 22:10 ` GNUtoo
2009-02-24 22:17 ` Tom Rini
2009-02-24 22:29 ` Phil Blundell
2009-02-24 22:42 ` GNUtoo
2009-02-25 9:09 ` Richard Purdie
2009-02-25 23:04 ` Denys Dmytriyenko
2009-02-26 13:28 ` Richard Purdie
2009-02-27 0:20 ` Otavio Salvador
2009-02-24 18:01 ` Otavio Salvador
2009-02-24 18:36 ` Ihar Hrachyshka
2009-02-24 18:50 ` Tom Rini
2009-02-24 22:20 ` GNUtoo
2009-02-25 2:01 ` Otavio Salvador
2009-02-25 2:25 ` Tom Rini
2009-02-25 9:01 ` Richard Purdie
2009-02-25 21:27 ` Vitus Jensen
2009-02-25 21:35 ` Tom Rini
2009-02-25 22:04 ` Vitus Jensen
2009-02-26 8:10 ` Koen Kooi [this message]
2009-02-26 12:50 ` Bernhard Guillon
2009-02-28 9:57 ` Alessandro GARDICH
2009-02-28 10:45 ` Koen Kooi
2009-02-28 10:51 ` Alessandro GARDICH
2009-02-28 13:12 ` Philip Balister
2009-02-24 20:29 ` Bernhard Guillon
2009-02-24 22:45 ` GNUtoo
2009-02-25 9:16 ` Koen Kooi
-- strict thread matches above, loose matches on Subject: below --
2009-02-24 20:00 Frans Meulenbroeks
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='go5ipr$nvl$1@ger.gmane.org' \
--to=k.kooi@student.utwente.nl \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@openembedded.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.