From: Michael Olbrich <m.olbrich@pengutronix.de>
To: Christian Melki <christian.melki@t2data.com>
Cc: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH] xz: Version bump. 5.4.0 -> 5.4.2
Date: Thu, 23 Mar 2023 06:43:09 +0100 [thread overview]
Message-ID: <ZBvm7eSkW4miA7WM@pengutronix.de> (raw)
In-Reply-To: <20230321204644.3940162-1-christian.melki@t2data.com>
On Tue, Mar 21, 2023 at 09:46:44PM +0100, Christian Melki wrote:
> Mostly bugfixes.
> License files changed, all of them according to md5.
> Yet I can only find changes in COPYING and COPYING.GPLv3.
> Same story goes for the git repo and the change dates.
> Really strange. But both of the real changes are minor.
I think you mixed up something here. Im getting:
ptxdist: error:
checksum of license file '.../build-host/xz-5.4.2/COPYING.GPLv2'
changed: 1ebbd3e34237af26da5dc08a4e440464 -> b234ee4d69f5fce4486a80fdaf4a4263
Michael
> XZ-utils could also use a tool cleanup.
> I find it unlikely that an embedded target will use all the tools or none.
> Compression, decompression and a cat softlink should cover most
> usage scenarios.
>
> Signed-off-by: Christian Melki <christian.melki@t2data.com>
> ---
> rules/xz.make | 12 ++++++------
> 1 file changed, 6 insertions(+), 6 deletions(-)
>
> diff --git a/rules/xz.make b/rules/xz.make
> index bf019c9d8..491649a3c 100644
> --- a/rules/xz.make
> +++ b/rules/xz.make
> @@ -14,8 +14,8 @@ PACKAGES-$(PTXCONF_XZ) += xz
> #
> # Paths and names
> #
> -XZ_VERSION := 5.4.0
> -XZ_MD5 := 2cc95f33fe0527622177b2bb2f5956c8
> +XZ_VERSION := 5.4.2
> +XZ_MD5 := 9b906c14f21744ca21018d5fc3054ecd
> XZ := xz-$(XZ_VERSION)
> XZ_SUFFIX := tar.bz2
> XZ_URL := http://tukaani.org/xz/$(XZ).$(XZ_SUFFIX)
> @@ -23,10 +23,10 @@ XZ_SOURCE := $(SRCDIR)/$(XZ).$(XZ_SUFFIX)
> XZ_DIR := $(BUILDDIR)/$(XZ)
> XZ_LICENSE := public_domain AND LGPL-2.1-or-later AND GPL-2.0-or-later AND GPL-3.0-or-later
> XZ_LICENSE_FILES := \
> - file://COPYING;md5=97d554a32881fee0aa283d96e47cb24a \
> - file://COPYING.GPLv2;md5=b234ee4d69f5fce4486a80fdaf4a4263 \
> - file://COPYING.GPLv3;md5=d32239bcb673463ab874e80d47fae504 \
> - file://COPYING.LGPLv2.1;md5=4fbd65380cdd255951079008b364516c
> + file://COPYING;md5=c8ea84ebe7b93cce676b54355dc6b2c0 \
> + file://COPYING.GPLv2;md5=1ebbd3e34237af26da5dc08a4e440464 \
> + file://COPYING.GPLv3;md5=b234ee4d69f5fce4486a80fdaf4a4263 \
> + file://COPYING.LGPLv2.1;md5=b234ee4d69f5fce4486a80fdaf4a4263
>
> # ----------------------------------------------------------------------------
> # Prepare
> --
> 2.34.1
>
>
>
--
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 |
prev parent reply other threads:[~2023-03-23 5:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-21 20:46 Christian Melki
2023-03-23 5:43 ` Michael Olbrich [this message]
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=ZBvm7eSkW4miA7WM@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=christian.melki@t2data.com \
--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