Openembedded Core Discussions
 help / color / mirror / Atom feed
From: bruce.ashfield@gmail.com
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: Adrian Freihofer <adrian.freihofer@siemens.com>,
	openembedded-core@lists.openembedded.org
Subject: Re: [OE-core][RFC PATCH 0/8] enhance kernel -devsrc output options
Date: Fri,  6 Nov 2026 15:20:38 -0500	[thread overview]
Message-ID: <20261106202038.4192004-1-bruce.ashfield@gmail.com> (raw)
In-Reply-To: <22b23081715a48206765902938899bb7f9af3be0.camel@linuxfoundation.org>

From: Bruce Ashfield <bruce.ashfield@gmail.com>

On Fri, 2026-11-06 at 14:08 -0500, Richard Purdie wrote:
> On Fri, 2026-11-06 at 12:32 -0500, bruce.ashfield@gmail.com wrote:
> >   7-8: two general oe-core fixes, for issues I noticed in the debug
> >        rootfs while working on this support. They aren't kernel
> >        specific and don't depend on the rest of the series:
> >        postinsts of debug only packages being registered against the
> >        image, and IMAGE_INSTALL_DEBUGFS packages with broken
> >        dependencies being silently skipped.
>
> Do you have an example of something which has a postinst which this
> pulls in? I'm wondering why debug src packages have postinsts :/

They don't :) Nothing in the -devsrc part of the series has a postinst,
and neither do the complementary -dbg packages.

I hit it while prototyping the versioned package, which originally used
a postinst for the /usr/src symlink (dropped, the link is now a plain
file owned by kernel-devsrc). I then reproduced it with a test recipe
using pkg_postinst_ontarget. I could dig up that reproducer and send
it along. I should have mentioned that in the series send.

The general case is that IMAGE_INSTALL_DEBUGFS takes any package. If
one that is only in the debug rootfs has a postinst that defers to
first boot, it gets registered in the intercepts the image shares, and
do_rootfs fails trying to save a postinst for a package that isn't in
the image. In oe-core, gnutls-fips and openssl-ossl-module-fips are the
obvious candidates, though I haven't built either into a debug rootfs.

So it's not needed by this series anymore. I'm happy to split 7-8 out
and send them separately, or chuck it in the bin if it isn't necessary.
I'll run it locally, since I don't throw much away!

Bruce

>
> Cheers,
>
> Richard

      reply	other threads:[~2026-11-06 20:20 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-06 17:32 [OE-core][RFC PATCH 0/8] enhance kernel -devsrc output options bruce.ashfield
2026-11-06 17:32 ` [OE-core][RFC PATCH 01/08] kernel.bbclass: map the kernel build directory to KERNEL_SRC_PATH bruce.ashfield
2026-11-06 17:32 ` [OE-core][RFC PATCH 02/08] kernel.bbclass: stage a manifest of the source files the build read bruce.ashfield
2026-11-06 17:32 ` [OE-core][RFC PATCH 03/08] kernel-devsrc: add build and source PACKAGECONFIG levels bruce.ashfield
2026-11-06 17:32 ` [OE-core][RFC PATCH 04/08] kernel-devsrc: add full and tarball " bruce.ashfield
2026-11-06 17:32 ` [OE-core][RFC PATCH 05/08] kernel-devsrc: optionally version the package bruce.ashfield
2026-11-06 17:32 ` [OE-core][RFC PATCH 06/08] kernel-devsrc: skip the recipe if no PACKAGECONFIG level is set bruce.ashfield
2026-11-06 17:32 ` [OE-core][RFC PATCH 07/08] rootfs: don't carry debug rootfs postinst registrations into the image bruce.ashfield
2026-11-06 17:32 ` [OE-core][RFC PATCH 08/08] rootfs: fail if an IMAGE_INSTALL_DEBUGFS package can't be installed bruce.ashfield
2026-11-06 19:08 ` [OE-core][RFC PATCH 0/8] enhance kernel -devsrc output options Richard Purdie
2026-11-06 20:20   ` bruce.ashfield [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=20261106202038.4192004-1-bruce.ashfield@gmail.com \
    --to=bruce.ashfield@gmail.com \
    --cc=adrian.freihofer@siemens.com \
    --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