From: Trevor Woerner <twoerner@gmail.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH] bmaptool: now part of Yocto Project
Date: Tue, 5 Mar 2024 07:52:46 -0500 [thread overview]
Message-ID: <20240305125245.GA2252@localhost> (raw)
In-Reply-To: <0e8ffac6e98c84bf7665acbbe33eef05742e8109.camel@linuxfoundation.org>
On Tue 2024-03-05 @ 11:59:17 AM, Richard Purdie wrote:
> On Mon, 2024-03-04 at 14:25 -0500, Trevor Woerner wrote:
> > The bmaptool (previously: bmap-tools, bmap-tool, bmaptool) has been moved
> > to be under the Yocto Project umbrella and is now hosted at:
> >
> > github.com/yoctoproject/bmaptool
> >
> > Signed-off-by: Trevor Woerner <twoerner@gmail.com>
> > ---
> > meta/classes-recipe/image_types.bbclass | 2 +-
> > meta/classes-recipe/image_types_wic.bbclass | 2 +-
> > meta/conf/distro/include/maintainers.inc | 2 +-
> > .../bmap-tools_git.bb => bmaptool/bmaptool_git.bb} | 8 ++++----
> > .../files/0001-BmapCopy.py-fix-error-message.patch | 0
> > ...0002-CLI.py-fix-block-device-udev-race-condition.patch | 0
> > .../0003-BmapCopy.py-tweak-suggested-udev-rule.patch | 0
> > 7 files changed, 7 insertions(+), 7 deletions(-)
> > rename meta/recipes-support/{bmap-tools/bmap-tools_git.bb => bmaptool/bmaptool_git.bb} (78%)
> > rename meta/recipes-support/{bmap-tools => bmaptool}/files/0001-BmapCopy.py-fix-error-message.patch (100%)
> > rename meta/recipes-support/{bmap-tools => bmaptool}/files/0002-CLI.py-fix-block-device-udev-race-condition.patch (100%)
> > rename meta/recipes-support/{bmap-tools => bmaptool}/files/0003-BmapCopy.py-tweak-suggested-udev-rule.patch (100%)
>
> Thanks. Unfortunately this wasn't quite enough and caused a ton of
> build failures, it also needs:
Oops! Sorry about that.
> diff --git a/meta/recipes-core/meta/wic-tools.bb b/meta/recipes-core/meta/wic-tools.bb
> index 9282d36a4dc..76494e7fca4 100644
> --- a/meta/recipes-core/meta/wic-tools.bb
> +++ b/meta/recipes-core/meta/wic-tools.bb
> @@ -4,7 +4,7 @@ LICENSE = "MIT"
>
> DEPENDS = "\
> parted-native gptfdisk-native dosfstools-native \
> - mtools-native bmap-tools-native grub-native cdrtools-native \
> + mtools-native bmaptool-native grub-native cdrtools-native \
> btrfs-tools-native squashfs-tools-native pseudo-native \
> e2fsprogs-native util-linux-native tar-native erofs-utils-native \
> virtual/${TARGET_PREFIX}binutils \
> diff --git a/scripts/lib/wic/misc.py b/scripts/lib/wic/misc.py
> index 2b90821b305..1a7c140fa6c 100644
> --- a/scripts/lib/wic/misc.py
> +++ b/scripts/lib/wic/misc.py
> @@ -25,7 +25,7 @@ from wic import WicError
> logger = logging.getLogger('wic')
>
> # executable -> recipe pairs for exec_native_cmd
> -NATIVE_RECIPES = {"bmaptool": "bmap-tools",
> +NATIVE_RECIPES = {"bmaptool": "bmaptool",
> "dumpe2fs": "e2fsprogs",
> "grub-mkimage": "grub-efi",
> "isohybrid": "syslinux",
>
> but I'll squash that into the patch.
Great, thanks!
next prev parent reply other threads:[~2024-03-05 12:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-04 19:25 [PATCH] bmaptool: now part of Yocto Project Trevor Woerner
2024-03-05 11:59 ` [OE-core] " Richard Purdie
2024-03-05 12:52 ` Trevor Woerner [this message]
2024-03-05 19:17 ` Khem Raj
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=20240305125245.GA2252@localhost \
--to=twoerner@gmail.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