From: Alejandro Hernandez <alejandro.hernandez@linux.intel.com>
To: Christopher Larson <clarson@kergoth.com>
Cc: bitbake-devel@lists.openembedded.org
Subject: Re: [PATCH v2] fetcher: fix BB_STRICT_CHECKSUM datatype check
Date: Thu, 09 Oct 2014 15:22:42 -0500 [thread overview]
Message-ID: <5436EE92.1010308@linux.intel.com> (raw)
In-Reply-To: <CABcZAN=+nJjhKpGXnshy-VuFdW85oXwG5V9KsPMe79qm5cWXsQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1948 bytes --]
It does not change behavior but it forces the value to be a string,
avoiding related problems when performing comparisons on "strict",
another option as Richard Purdie suggested would be to import the
boolean function from /meta/lib/oe/types.py in OE-Core into a new types
module in bitbake, forcing it to get a "good" value that we could then use.
On 08/10/14 11:13, Christopher Larson wrote:
>
> On Tue, Sep 30, 2014 at 9:21 AM, Alejandro Hernandez
> <alejandro.hernandez@linux.intel.com
> <mailto:alejandro.hernandez@linux.intel.com>> wrote:
>
> Forcing strict to be a string, to avoid problems when performing
> comparisons
>
> [YOCTO #6762]
>
> Signed-off-by: Alejandro Hernandez
> <alejandro.hernandez@linux.intel.com
> <mailto:alejandro.hernandez@linux.intel.com>>
> ---
> lib/bb/fetch2/__init__.py | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/lib/bb/fetch2/__init__.py b/lib/bb/fetch2/__init__.py
> index df2f2b0..10c3346 100644
> --- a/lib/bb/fetch2/__init__.py
> +++ b/lib/bb/fetch2/__init__.py
> @@ -543,8 +543,8 @@ def verify_checksum(ud, d):
>
> if ud.method.recommends_checksum(ud):
> # If strict checking enabled and neither sum defined,
> raise error
> - strict = d.getVar("BB_STRICT_CHECKSUM", True) or None
> - if strict and not (ud.md5_expected or ud.sha256_expected):
> + strict = d.getVar("BB_STRICT_CHECKSUM", "1") or "0"
> + if (strict == "1") and not (ud.md5_expected or
> ud.sha256_expected):
>
>
> Why was True (second argument of getVar) changed to "1" here? It
> violates our conventions and doesn't actually change anything in the
> behavior.
> --
> Christopher Larson
> clarson at kergoth dot com
> Founder - BitBake, OpenEmbedded, OpenZaurus
> Maintainer - Tslib
> Senior Software Engineer, Mentor Graphics
[-- Attachment #2: Type: text/html, Size: 3625 bytes --]
next prev parent reply other threads:[~2014-10-09 20:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-30 16:21 [PATCH v2] fetcher: fix BB_STRICT_CHECKSUM datatype check Alejandro Hernandez
2014-10-08 16:13 ` Christopher Larson
2014-10-09 20:22 ` Alejandro Hernandez [this message]
2014-10-09 20:27 ` Christopher Larson
2014-10-09 20:38 ` Alejandro Hernandez
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=5436EE92.1010308@linux.intel.com \
--to=alejandro.hernandez@linux.intel.com \
--cc=bitbake-devel@lists.openembedded.org \
--cc=clarson@kergoth.com \
/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.