All of lore.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: Christophe PRIOUZEAU <christophe.priouzeau@st.com>
Cc: "openembedded-devel@lists.openembedded.org"
	<openembedded-devel@lists.openembedded.org>
Subject: Re: [PATCH] python-script: update license md5sum
Date: Thu, 29 Aug 2019 18:51:22 +0300	[thread overview]
Message-ID: <20190829155122.GA17820@localhost> (raw)
In-Reply-To: <20190829143506.19291-1-christophe.priouzeau@st.com>

On Thu, Aug 29, 2019 at 02:35:07PM +0000, Christophe PRIOUZEAU wrote:
> Update md5sum of license file.
>...
> --- a/meta-python/recipes-devtools/python/python-scrypt.inc
> +++ b/meta-python/recipes-devtools/python/python-scrypt.inc
> @@ -1,6 +1,6 @@
>  DESCRIPTION = "Bindings for the scrypt key derivation function library"
>  LICENSE = "BSD-2-Clause"
> -LIC_FILES_CHKSUM = "file://${COMMON_LICENSE_DIR}/BSD-2-Clause;md5=8bef8e6712b1be5aa76af1ebde9d6378"
> +LIC_FILES_CHKSUM = "file://${COMMON_LICENSE_DIR}/BSD-2-Clause;md5=cb641bc04cda31daea161b1bc15da69f"
>...

The actual problem is that this does not do what LIC_FILES_CHKSUM is 
supposed to do.

LIC_FILES_CHKSUM should verify that the license information in the 
software hasn't changed when upgrading it.

These recipes check the copy of the license text in OE instead,
which wouldn't change if the license of python-scrypt would change.

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed



  reply	other threads:[~2019-08-29 15:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-29 14:35 [PATCH] python-script: update license md5sum Christophe PRIOUZEAU
2019-08-29 15:51 ` Adrian Bunk [this message]
2019-08-29 18:44   ` Khem Raj
2019-08-29 19:30     ` Adrian Bunk

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=20190829155122.GA17820@localhost \
    --to=bunk@stusta.de \
    --cc=christophe.priouzeau@st.com \
    --cc=openembedded-devel@lists.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.