All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Rini <trini@kernel.crashing.org>
To: openembedded-devel@openembedded.org
Subject: Re: checksums situation
Date: Tue, 24 Feb 2009 08:02:47 -0700	[thread overview]
Message-ID: <20090224150247.GG2172@smtp.west.cox.net> (raw)
In-Reply-To: <200902240949.10862.openembedded@haerwu.biz>

On Tue, Feb 24, 2009 at 09:49:04AM +0100, Marcin Juszkiewicz wrote:
> On Tuesday 24 of February 2009 07:46:39 Tom Rini wrote:
> 
> > And, is anyone doing more then 'cat tmp/checksums.ini >>
> > openembedded/conf/checksums.ini && python the-sorter' ?  And by more
> > I mean check for an upstream .md5 or similar, to make sure this is
> > really right?
> 
> commit 67aa127f4b4cb2e4083a02adfddd7d82534751a3
> Author: Marcin Juszkiewicz <hrw@openembedded.org>
> Date:   Thu Nov 13 18:07:47 2008 +0100
> 
>     checksums.ini: add 1212 entries from test fetch build
> 
>     This is result of simple shell script and few hours of fetching:
>     for recipe in $OEROOT/packages/*/*.bb
>     do
>       bitbake -b $recipe -cfetch
>     done
> 
> This was done with not so empty DL_DIR but most of entries were fresh 
> fetched. If someone has machine with good network connection (I no 
> longer have access to machine where I was running that test) then feel 
> free to call that loop with empty DL_DIR.

IOW, no.  We're just using checksums.ini as a "at one point, it was ..."
and not actually making sure that it's the right checksum.

-- 
Tom Rini



  reply	other threads:[~2009-02-24 15:05 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 [this message]
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
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=20090224150247.GG2172@smtp.west.cox.net \
    --to=trini@kernel.crashing.org \
    --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.