Missing 'mender-clientpackagegroup-core-buildessential'

zhalat · May 7, 2024, 8:54am

Hi,
I am trying to integrate mender with dunfell yocto project for target stm32mpu153.
I have followed for available doc and examples and here is:

mender port layer
stm32mpu_mender_port_layer
system manifest

<?xml version="1.0" encoding="UTF-8"?>
<manifest>
  <remote fetch="ssh://git@bitbucket.org/electricityexchange" name="viotas"/>
  <remote fetch="https://github.com" name="github"/>
  <remote fetch="http://git.openembedded.org" name="oe"/>
  <remote fetch="https://github.com/STMicroelectronics" name="OpenSTLinux"/>
  <remote fetch="https://github.com/mendersoftware" name="mender"/>
  
  <default remote="OpenSTLinux"/>
  
  <project name="yocto_env" remote="viotas" revision="dunfell/umeter" path="."/>
  <project name="meta-um-bsp" remote="viotas" revision="vio-um0025A" path="layers/meta-um-bsp"/>
  <project name="meta-vio-business" remote="viotas" revision="master" path="layers/meta-vio-business"/>
  <project name="meta-mender-st-stm32mp15x-port" remote="viotas" revision="master" path="layers/meta-mender-community/meta-mender-st-stm32mp">
      <linkfile src="scripts/stm32mp-setup-mender.sh" dest="stm32mp-setup-mender.sh"/>
  </project>

  <project name="bitbake" path="layers/openembedded-core/bitbake" remote="oe" revision="a394eeec6aeb98c6395cb5da2036ce936bdaa0a0"/>
  <project name="meta-openembedded" path="layers/meta-openembedded" remote="oe" revision="5bba79488b7d393d2258d6e917f7bf7b0d7c4073"/>
  <project name="meta-qt5/meta-qt5" path="layers/meta-qt5" remote="github" revision="0d8eb956015acdea7e77cd6672d08dce18061510"/>
  <project name="meta-st-openstlinux" path="layers/meta-st/meta-st-openstlinux" revision="d6947f5a1898744aa15a96b68e8945f4f553175e"/>
  <project name="meta-st-stm32mp" path="layers/meta-st/meta-st-stm32mp" revision="7b55c34159fcfd57b4965f7aa9284200eea09d20"/>
  <project name="meta-st-stm32mp-addons" path="layers/meta-st/meta-st-stm32mp-addons" revision="81065195a63e98be8f423ab422960e9d7896f4d5"/>
  <project name="meta-st-scripts" path="layers/meta-st/scripts" revision="d2ba39bc40952ff6eb06d2b0e496910a74209660"/>
  <project name="openembedded-core" path="layers/openembedded-core" remote="oe" revision="72431ee8de5e3a53d259cebf420a7713ac9e1f14"/>
  <project name="meta-mender" remote="mender" revision="dunfell" path="layers/meta-mender"/>
  <project name="meta-mender-community" remote="mender" revision="dunfell" path="layers/meta-mender-community"/>
</manifest>

layer integration just before build

./stm32mp-setup-mender.sh

layer                 path                                      priority
==========================================================================
meta-python           /var/work/jenkins/micrometer_sd/to_del/layers/meta-openembedded/meta-python  7
meta-oe               /var/work/jenkins/micrometer_sd/to_del/layers/meta-openembedded/meta-oe  6
meta-vio-business     /var/work/jenkins/micrometer_sd/to_del/layers/meta-vio-business  10
meta-um-bsp           /var/work/jenkins/micrometer_sd/to_del/layers/meta-um-bsp  1
meta-gnome            /var/work/jenkins/micrometer_sd/to_del/layers/meta-openembedded/meta-gnome  7
meta-initramfs        /var/work/jenkins/micrometer_sd/to_del/layers/meta-openembedded/meta-initramfs  8
meta-multimedia       /var/work/jenkins/micrometer_sd/to_del/layers/meta-openembedded/meta-multimedia  6
meta-networking       /var/work/jenkins/micrometer_sd/to_del/layers/meta-openembedded/meta-networking  5
meta-webserver        /var/work/jenkins/micrometer_sd/to_del/layers/meta-openembedded/meta-webserver  6
meta-filesystems      /var/work/jenkins/micrometer_sd/to_del/layers/meta-openembedded/meta-filesystems  6
meta-perl             /var/work/jenkins/micrometer_sd/to_del/layers/meta-openembedded/meta-perl  6
meta-st-stm32mp       /var/work/jenkins/micrometer_sd/to_del/layers/meta-st/meta-st-stm32mp  6
meta-qt5              /var/work/jenkins/micrometer_sd/to_del/layers/meta-qt5  7
meta-mender-core      /var/work/jenkins/micrometer_sd/to_del/layers/meta-mender/meta-mender-core  6
meta-mender-demo      /var/work/jenkins/micrometer_sd/to_del/layers/meta-mender/meta-mender-demo  10
meta-mender-st-stm32mp  /var/work/jenkins/micrometer_sd/to_del/layers/meta-mender-community/meta-mender-st-stm32mp  92
meta-st-openstlinux   /var/work/jenkins/micrometer_sd/to_del/layers/meta-st/meta-st-openstlinux  5
meta                  /var/work/jenkins/micrometer_sd/to_del/layers/openembedded-core/meta  5

The issue:

NOTE: Resolving any missing task queue dependencies
ERROR: Nothing RPROVIDES 'mender-clientpackagegroup-core-buildessential' (but /var/work/jenkins/micrometer_sd/to_del/layers/meta-vio-business/recipes-core/images/um-image-full.bb RDEPENDS on or otherwise requires it)
NOTE: Runtime target 'mender-clientpackagegroup-core-buildessential' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['mender-clientpackagegroup-core-buildessential']
ERROR: Required build target 'um-image-full' has no buildable providers.
Missing or unbuildable dependency chain was: ['um-image-full', 'mender-clientpackagegroup-core-buildessential']

I figured out an example I have built did not required that packet.
Is it possible that our yocto project is set in such a way that the packet is required but it is not by default?

zhalat · May 7, 2024, 11:11am

I had to comment:
IMAGE_INSTALL_append = "packagegroup-core-buildessential
in our yocto project to get rid of the error…

TheYoctoJester · May 7, 2024, 11:31am

Hi @zhalat,

The line indicates two problems:

a very old Yocto release, as the syntax is :append since more than 3 years by now (and actually supported on dunfell- which is end of life)
a bug in your project anyways, as the append mechanism does not add a leading space, so it needs to be ...append = " packagegroup-core-buildessential"

Greets,
Josef

zhalat · May 14, 2024, 3:13pm

hello agin.
I came back to integration with our Yocto.
According to manifest.xml we use dunfell for stm32mp1 and dunfell for mender.
Yocto usues u-boot in version v2020.10
commit 050acee119b3757fee3bd128f55d720fdd9bb890 (HEAD → master, tag: v2020.10)
I’m trying to build u-boot recepie.

bitbake -c fetch u-boot # u-boot in ver (HEAD → master, tag: v2020.10) is downloaded
bitbake -c patch u-boot # apply local patches

    NOTE: Executing Tasks
    WARNING: u-boot-stm32mp-2020.10.r1-r0 do_patch: Fuzz detected:

    Applying patch 0003-Integration-of-Mender-boot-code-into-U-Boot.patch
    patching file include/env_default.h
    Hunk #1 succeeded at 10 with fuzz 2 (offset 1 line).
    Hunk #2 succeeded at 24 (offset 1 line).
    patching file scripts/Makefile.autoconf
    Hunk #1 succeeded at 108 (offset -1 lines).

    The context lines in the patches can be updated with devtool:

        devtool modify u-boot-stm32mp
        devtool finish --force-patch-refresh u-boot-stm32mp <layer_path>

    Don't forget to review changes done by devtool!

    WARNING: u-boot-stm32mp-2020.10.r1-r0 do_patch: QA Issue: Patch log indicates that patches do not apply cleanly. [patch-fuzz]

bitbake u-boot
eventually u-boot built well.

But patching process bother me. Seems like patches from mender layer doesn’t applied well
That caught my attention. Our project uses old openstlinux: openstlinux-5.10-dunfell-mp1-21-03-31
(and for some reason must be such)

but mender layer is
<project name="meta-mender" remote="mender" revision="dunfell" path="layers/meta-mender"/>
which seems to be reasonably new.

Is it better to set
<project name="meta-mender" remote="mender" revision="dunfell-v2021.03" path="layers/meta-mender"/>
or keep mender layer up-to date for dunfell ?
Am asking because despite the fact u-boot goes well
buid stuck at

ERROR: Logfile of failure stored in: /var/work/jenkins/micrometer_sd/to_del/build-stbase-vio-um0025A/tmp-glibc/work/vio_um0025A-ostl-linux-gnueabi/st-image-resize-initrd/1.0-r0/temp/log.do_image_dataimg.4145095
Log data follows:
| DEBUG: Executing python function do_copy_rootfs
| DEBUG: Python function do_copy_rootfs finished
| DEBUG: Executing shell function do_install_bootstrap_artifact
| install: cannot create regular file 
'/var/work/jenkins/micrometer_sd/to_del/build-stbase-vio-um0025A/tmp-glibc/work/vio_um0025A-ostl-linux-gnueabi/st-image-resize-initrd/1.0-r0/data.copy.image_dataimg/mender/bootstrap.mender': No such file or directory

ERROR: Task (/var/work/jenkins/micrometer_sd/to_del/layers/meta-st/meta-st-openstlinux/recipes-st/images/st-image-resize-initrd.bb:do_image_dataimg) failed with exit code '1'

Topic		Replies	Views
Yocto version General Discussions	11	808	June 23, 2021
Mender-connect unable to connect to server General Discussions yocto , mender-client	2	420	January 26, 2024
Didn't find service unit 'mender-client.service' General Discussions mender-client , dunfell , kirkstone	4	1021	April 10, 2023
Simple configuration (dunfell) General Discussions	29	2411	March 9, 2021
Mender-configure: Files installed but not shipped General Discussions yocto	13	781	May 31, 2023

Missing 'mender-clientpackagegroup-core-buildessential'

Related topics