All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bruce Ashfield <bruce.ashfield@gmail.com>
To: Ross Burton <Ross.Burton@arm.com>
Cc: Luca Ceresoli <luca.ceresoli@bootlin.com>,
	"openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>, nd <nd@arm.com>
Subject: Re: [OE-core] [PATCH 9/9] lzo: remove recipe from oe-core
Date: Wed, 25 May 2022 09:55:15 -0400	[thread overview]
Message-ID: <CADkTA4OAQkOiV44gR+rdurZQb7U+qPaUGO5ZYZwYU72agSPqsQ@mail.gmail.com> (raw)
In-Reply-To: <PA4PR08MB7411343691EFAFDEA1EEE9C7E8D69@PA4PR08MB7411.eurprd08.prod.outlook.com>

On Wed, May 25, 2022 at 9:46 AM Ross Burton <Ross.Burton@arm.com> wrote:
>
> Yes, it mainly blew up because the tested oe-core branch had the removal of lzo but meta-oe didn’t have the addition.
>
>
>
> Would you like a resend of the xen patch to add an option, but leave it as enabled?  Or will you merge this patch which disables lzo?
>
>


The patch is fine as-is. If someone needs it on by default, they can
scream and send a patch to change that status :) It will still be
available, so they can easily carry bbappend with a packageconfig.

Bruce



>
> Ross
>
>
>
> From: Bruce Ashfield <bruce.ashfield@gmail.com>
> Date: Wednesday, 25 May 2022 at 13:59
> To: Ross Burton <Ross.Burton@arm.com>
> Cc: Luca Ceresoli <luca.ceresoli@bootlin.com>, openembedded-core@lists.openembedded.org <openembedded-core@lists.openembedded.org>, nd <nd@arm.com>
> Subject: Re: [OE-core] [PATCH 9/9] lzo: remove recipe from oe-core
>
>
>
>
>
> On Wed, May 25, 2022 at 7:26 AM Ross Burton <Ross.Burton@arm.com> wrote:
>
> On 25 May 2022, at 09:03, Luca Ceresoli <luca.ceresoli@bootlin.com> wrote:
> >
> > Hi Ross, Bruce,
> >
> > Il giorno Tue, 24 May 2022 16:24:01 +0100
> > "Ross Burton" <ross.burton@arm.com> ha scritto:
> >
> >> LZO is a fairly archaic compression format that hasn't been updated
> >> since 2017.  It's now unused by anything else in oe-core, so remove
> >> the recipes.
> >>
> >> Signed-off-by: Ross Burton <ross.burton@arm.com>
> >
> > I love removals of archaic features...
> >
> > ...and how they make things explode :-)
> >
> > stdio: ERROR: Nothing PROVIDES 'lzo' (but
> > /home/pokybuild/yocto-worker/meta-virt/build/meta-virtualization/recipes-extended/xen/xen_4.16.bb,
> > /home/pokybuild/yocto-worker/meta-virt/build/meta-virtualization/recipes-extended/xen/xen-tools_4.16.bb
> > DEPENDS on or otherwise requires it)
>
> I’ve also just sent a RFC patch for xen to disable LZO entirely, but I’ll leave that up to Bruce to decide.  If lzo is removed from core it will be added to meta-oe, so xen will continue to build either way.
>
>
>
> right.
>
>
>
> We'll keep it as optional.
>
>
>
> But isn't this just a timing issue for the failure ? Or are we missing a dependency in meta-virt on where this landed in meta-oe ? We definitely have meta-oe dependencies in meta-virt, so the AB should already have those in place .. so this must have only blown up because it hasn't landed in meta-oe yet (nor should it probably have, as this is a test of the removal in OEcore) .
>
>
>
> Either way, I'll merge the meta-virt, make-it-optional patch shortly and this should be good to go.
>
>
>
> Bruce
>
>
>
>
>
> Ross
>
>
>
>
> --
>
> - Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end
> - "Use the force Harry" - Gandalf, Star Trek II



-- 
- Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end
- "Use the force Harry" - Gandalf, Star Trek II


  reply	other threads:[~2022-05-25 13:55 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-24 15:23 [PATCH 1/9] lzo: Add further info to a patch Ross Burton
2022-05-24 15:23 ` [PATCH 2/9] btrfs-tools: add a PACKAGECONFIG for lzo Ross Burton
2022-05-24 15:23 ` [PATCH 3/9] mtd-utils: disable LZO by default Ross Burton
2022-05-25  9:33   ` [OE-core] " richard.purdie
2022-05-25 10:34     ` Ross Burton
2022-05-25 11:38       ` richard.purdie
2022-05-24 15:23 ` [PATCH 4/9] squashfs-tools: " Ross Burton
2022-05-24 15:23 ` [PATCH 5/9] libarchive: " Ross Burton
2022-05-24 15:23 ` [PATCH 6/9] lzop: remove recipe from oe-core Ross Burton
2022-05-24 15:23 ` [PATCH 7/9] oeqa/selftest/imagefeatures: don't exercise lzo compression Ross Burton
2022-05-24 15:24 ` [PATCH 8/9] packagegroup-self-hosted: remove lzo Ross Burton
2022-05-24 15:24 ` [PATCH 9/9] lzo: remove recipe from oe-core Ross Burton
2022-05-25  8:03   ` [OE-core] " Luca Ceresoli
2022-05-25 11:26     ` Ross Burton
2022-05-25 12:59       ` Bruce Ashfield
2022-05-25 13:45         ` Ross Burton
2022-05-25 13:55           ` Bruce Ashfield [this message]
2022-05-25  8:00 ` [OE-core] [PATCH 1/9] lzo: Add further info to a patch Luca Ceresoli

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=CADkTA4OAQkOiV44gR+rdurZQb7U+qPaUGO5ZYZwYU72agSPqsQ@mail.gmail.com \
    --to=bruce.ashfield@gmail.com \
    --cc=Ross.Burton@arm.com \
    --cc=luca.ceresoli@bootlin.com \
    --cc=nd@arm.com \
    --cc=openembedded-core@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.