From: "Mathieu Dubois-Briand" <mathieu.dubois-briand@bootlin.com>
To: <ross.burton@arm.com>, <openembedded-core@lists.openembedded.org>
Cc: <twoerner@gmail.com>
Subject: Re: [OE-core] [PATCH 2/2] gptfdisk: remove recipe
Date: Tue, 11 Aug 2026 20:48:37 +0200 [thread overview]
Message-ID: <DKMC7ZM6NDM7.3U64VA8LP2GYM@bootlin.com> (raw)
In-Reply-To: <20260811153619.2048639-2-ross.burton@arm.com>
On Tue Aug 11, 2026 at 5:36 PM CEST, Ross Burton via lists.openembedded.org wrote:
> There are no dependencies on this recipe in oe-core or meta-oe now, as
> the standard fdisk command in util-linux has both a scriptable frontend
> and supports GPT partition tables.
>
> Also the last release was in 2024 and there's very little activity
> upstream.
>
> As such, remove the recipe.
>
And break the build :)
Looks like we do have a dependency on gptfdisk-native. Maybe this match
in meta-yocto?
meta-yocto-bsp/conf/machine/include/genericx86-common.inc:do_image_wic[depends] += "gptfdisk-native:do_populate_sysroot"
Here is the error:
ERROR: Nothing PROVIDES 'gptfdisk-native'. Close matches:
gperf-native
gtk+3-native
gtk4-native
ERROR: Nothing RPROVIDES 'core-image-sato'
No eligible RPROVIDERs exist for 'core-image-sato'
NOTE: Runtime target 'core-image-sato' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['core-image-sato']
ERROR: Nothing RPROVIDES 'core-image-sato-sdk'
No eligible RPROVIDERs exist for 'core-image-sato-sdk'
NOTE: Runtime target 'core-image-sato-sdk' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['core-image-sato-sdk']
ERROR: Nothing RPROVIDES 'core-image-minimal'
No eligible RPROVIDERs exist for 'core-image-minimal'
NOTE: Runtime target 'core-image-minimal' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['core-image-minimal']
ERROR: Nothing RPROVIDES 'core-image-full-cmdline'
No eligible RPROVIDERs exist for 'core-image-full-cmdline'
NOTE: Runtime target 'core-image-full-cmdline' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['core-image-full-cmdline']
https://autobuilder.yoctoproject.org/valkyrie/#/builders/4/builds/4388
https://autobuilder.yoctoproject.org/valkyrie/#/builders/19/builds/4362
https://autobuilder.yoctoproject.org/valkyrie/#/builders/65/builds/4336
...
Thanks,
Mathieu
--
Mathieu Dubois-Briand, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2026-08-11 18:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-11 15:36 [PATCH 1/2] wic: remove gptfdisk dependency Ross Burton
2026-08-11 15:36 ` [PATCH 2/2] gptfdisk: remove recipe Ross Burton
2026-08-11 18:48 ` Mathieu Dubois-Briand [this message]
2026-08-11 19:45 ` [OE-core] " Ross Burton
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=DKMC7ZM6NDM7.3U64VA8LP2GYM@bootlin.com \
--to=mathieu.dubois-briand@bootlin.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@arm.com \
--cc=twoerner@gmail.com \
/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.