From: Michael Olbrich <m.olbrich@pengutronix.de>
To: Artur Wiebe <artur@4wiebe.de>
Cc: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH] python3-pycparser: version bump 2.18 -> 2.21
Date: Tue, 30 Jan 2024 08:59:43 +0100 [thread overview]
Message-ID: <Zbisb7TjV9TPRFH7@pengutronix.de> (raw)
In-Reply-To: <20240129100553.56125-1-artur@4wiebe.de>
Hi,
On Mon, Jan 29, 2024 at 11:05:53AM +0100, Artur Wiebe wrote:
> LICENSE file change:
> "Slightly tweak the LICENSE file to be more canonical"
Please look at the differences of the file in the old and new version.
You'll note that the only difference is the copyright year.
The commit message you mentioned is from a change that was made _after_ the
new release.
The whole point of the checksum is, that we notice if something changes.
That means, actually looking at the files, comparing the two versions. So
we can decided if the license needs to be changed. And finally document the
whole process in the commit message.
If you are unsure what to do with a change then ask here on the list.
Regards,
Michael
> Signed-off-by: Artur Wiebe <artur@4wiebe.de>
> ---
> rules/python3-pycparser.make | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/rules/python3-pycparser.make b/rules/python3-pycparser.make
> index 484410713..a4a644778 100644
> --- a/rules/python3-pycparser.make
> +++ b/rules/python3-pycparser.make
> @@ -14,8 +14,8 @@ PACKAGES-$(PTXCONF_PYTHON3_PYCPARSER) += python3-pycparser
> #
> # Paths and names
> #
> -PYTHON3_PYCPARSER_VERSION := 2.18
> -PYTHON3_PYCPARSER_MD5 := 72370da54358202a60130e223d488136
> +PYTHON3_PYCPARSER_VERSION := 2.21
> +PYTHON3_PYCPARSER_MD5 := 48f7d743bf018f7bb2ffc5fb976d1492
> PYTHON3_PYCPARSER := pycparser-$(PYTHON3_PYCPARSER_VERSION)
> PYTHON3_PYCPARSER_SUFFIX := tar.gz
> PYTHON3_PYCPARSER_URL := $(call ptx/mirror-pypi, pycparser, $(PYTHON3_PYCPARSER).$(PYTHON3_PYCPARSER_SUFFIX))
> @@ -23,7 +23,7 @@ PYTHON3_PYCPARSER_SOURCE := $(SRCDIR)/$(PYTHON3_PYCPARSER).$(PYTHON3_PYCPARSER_S
> PYTHON3_PYCPARSER_DIR := $(BUILDDIR)/$(PYTHON3_PYCPARSER)
> PYTHON3_PYCPARSER_LICENSE := BSD-3-Clause
> PYTHON3_PYCPARSER_LICENSE_FILES := \
> - file://LICENSE;md5=86f1cedb4e6410a88ce8e30b91079169
> + file://LICENSE;md5=2c28cdeabcb88f5843d934381b4b4fea
>
> # ----------------------------------------------------------------------------
> # Prepare
> --
> 2.43.0
>
>
>
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
next prev parent reply other threads:[~2024-01-30 8:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-29 10:05 Artur Wiebe
2024-01-30 7:59 ` Michael Olbrich [this message]
2024-01-30 10:51 ` Artur Wiebe
-- strict thread matches above, loose matches on Subject: below --
2024-01-30 10:41 Artur Wiebe
2024-01-29 8:51 Artur Wiebe
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=Zbisb7TjV9TPRFH7@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=artur@4wiebe.de \
--cc=ptxdist@pengutronix.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox