Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Justin Bronder <jsbronder@cold-front.org>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: openembedded-core@lists.openembedded.org,
	Enrico Jorns <ejo@pengutronix.de>
Subject: Re: bitbake.conf: require lz4 instead of lz4c
Date: Wed, 6 Nov 2024 10:52:34 -0500	[thread overview]
Message-ID: <ZyuQwnMFmfIXDIaa@ravine.members.linode.com> (raw)
In-Reply-To: <3ac4b13ff08fc83cb2e37fc7caadeb89115e7814.camel@linuxfoundation.org>

On 06/11/24 07:50 +0000, Richard Purdie wrote:
> On Tue, 2024-11-05 at 10:37 -0500, Justin Bronder via lists.openembedded.org wrote:
> > With bitbake commit 'bb: compress: use lz4 instead of lz4c' we require
> > lz4, not lz4c [1].� Going as far back as Ubuntu 16.04/Fedora 25, they
> > are packaged together so it should be safe to simply adjust the
> > requirement from lz4c to lz4.
> > 
> > Note that the two are largely the same, but upstream has considered lz4c
> > deprecated since at least 2018 [2].
> > 
> > 1. https://git.openembedded.org/bitbake/commit/?id=907472034b344e4eb73cfd43059a413469f52e1c
> > 2. https://github.com/lz4/lz4/pull/553
> > 
> > Signed-off-by: Justin Bronder <jsbronder@cold-front.org>
> > ---
> > �meta/conf/bitbake.conf | 2 +-
> > �1 file changed, 1 insertion(+), 1 deletion(-)
> > 
> > diff --git a/meta/conf/bitbake.conf b/meta/conf/bitbake.conf
> > index eda505c861..14e761e2e7 100644
> > --- a/meta/conf/bitbake.conf
> > +++ b/meta/conf/bitbake.conf
> > @@ -517,7 +517,7 @@ HOSTTOOLS += " \
> > ���� [ ar as awk basename bash bunzip2 bzip2 cat chgrp chmod chown chrpath cmp comm cp cpio \
> > ���� cpp cut date dd diff diffstat dirname du echo egrep env expand expr false \
> > ���� fgrep file find flock g++ gawk gcc getconf getopt git grep gunzip gzip \
> > -��� head hostname iconv id install ld ldd ln ls lz4c make md5sum mkdir mkfifo mknod \
> > +��� head hostname iconv id install ld ldd ln ls lz4 make md5sum mkdir mkfifo mknod \
> > ���� mktemp mv nm objcopy objdump od patch perl pr printf pwd \
> > ���� python3 pzstd ranlib readelf readlink realpath rm rmdir rpcgen sed seq sh \
> > ���� sha1sum sha224sum sha256sum sha384sum sha512sum \
> > 
> 
> This caused a failure in barebox:
> 
> https://valkyrie.yoctoproject.org/#/builders/23/builds/409/steps/14/logs/stdio
> 

I see, sorry about that.

What would be the recommended path forward?

- Add lz4c to HOSTTOOLS_NONFATAL so it's still symlinked.  This would fix barebox and any other recipes that still depend on lz4c on distributions where lz4c is still packaged but leave others without an early warning system.
- Submit patches to barebox and others to use lz4 instead of lz4c.  This is probably more correct but will leave Tumbleweed unsupported by default with other distros to presumably follow.
- Convince Tumbleweed (and others) to continue packaging lz4c.


-- 
Justin Bronder


  reply	other threads:[~2024-11-06 15:52 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-05 15:37 [PATCH] bitbake.conf: require lz4 instead of lz4c Justin Bronder
2024-11-06  7:50 ` [OE-core] " Richard Purdie
2024-11-06 15:52   ` Justin Bronder [this message]
2024-11-06 16:01     ` Richard Purdie
2024-11-06 18:10       ` Justin Bronder
2024-11-06 16:03     ` [OE-core] " Alexander Kanavin
2024-11-12 13:20       ` Enrico Jörns
2024-11-12 13:34         ` Alexander Kanavin
2024-11-12 13:40           ` Enrico Jörns
2024-11-23 15:28             ` Guðni Már Gilbert
2024-11-25 18:21               ` Justin Bronder
2024-11-25 19:42                 ` Guðni Már Gilbert
2024-12-10  3:51                 ` [OE-core] " Denys Dmytriyenko
2024-12-10 15:15                   ` Justin Bronder

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=ZyuQwnMFmfIXDIaa@ravine.members.linode.com \
    --to=jsbronder@cold-front.org \
    --cc=ejo@pengutronix.de \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox