From: Martin Jansa <martin.jansa@gmail.com>
To: Clemens Lang <clemens.lang@bmw-carit.de>
Cc: bitbake-devel@lists.openembedded.org
Subject: Re: [PATCH] bitbake: fetch2: Revalidate checksums, YOCTO #5571
Date: Fri, 6 Mar 2015 13:22:38 +0100 [thread overview]
Message-ID: <20150306122238.GF2337@jama> (raw)
In-Reply-To: <20150306114328.GN5023@ulm-bmuc496424.bmw-carit.de>
[-- Attachment #1: Type: text/plain, Size: 1001 bytes --]
On Fri, Mar 06, 2015 at 12:43:28PM +0100, Clemens Lang wrote:
> Hello,
>
> On Fri, Feb 27, 2015 at 01:00:26PM +0100, Clemens Lang wrote:
> > Here's the patch, please review and consider applying:
>
> Any feedback on this? Anything I can do to get this reviewed?
FWIW: I like this, we were hit by this issue when the archive is
modified in premirror and builders are happily using it, because there
is .done file next to it.
This will at least fix the case when the file is intentionally modified
and checksums are updated in recipe to prevent re-using stalled file
from some premirror.
Using pickle is much better than counting the checksums on every
do_fetch.. we have GBs of sources and we don't want to spend extra
minutes on the build to re-check them if they are identical. Maybe add
the file time stamp as well, if the file was modified then .done could
be invalidated and checksums re-verified.
Regards,
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]
next prev parent reply other threads:[~2015-03-06 12:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-27 12:00 [PATCH] bitbake: fetch2: Revalidate checksums, YOCTO #5571 Clemens Lang
2015-03-06 11:43 ` Clemens Lang
2015-03-06 12:22 ` Martin Jansa [this message]
2015-03-06 13:03 ` Clemens Lang
2015-03-06 13:29 ` Martin Jansa
2015-03-06 13:42 ` Richard Purdie
2015-03-06 14:27 ` Clemens Lang
2015-03-06 14:28 ` Clemens Lang
-- strict thread matches above, loose matches on Subject: below --
2015-02-23 14:22 Clemens Lang
2015-02-26 14:42 ` Clemens Lang
2015-02-26 22:17 ` Alejandro Hernandez
2015-02-27 12:02 ` Clemens Lang
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=20150306122238.GF2337@jama \
--to=martin.jansa@gmail.com \
--cc=bitbake-devel@lists.openembedded.org \
--cc=clemens.lang@bmw-carit.de \
/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.