do_image_wic: No kickstart files from WKS_FILES were found: sdimage-dual-raspberrypi.wks #50

samannazz · 2023-01-05T09:41:39Z

samannazz
Jan 5, 2023

I am trying to do meta-rauc with Raspberry Pi 3, and I have followed the steps as mentioned. However, after baking the core-image-minimal, this error occurred.

what's the issue?

ERROR: core-image-minimal-1.0-r0 do_image_wic: No kickstart files from WKS_FILES were found: sdimage-dual-raspberrypi.wks core-image-minimal.wks. Please set WKS_FILE or WKS_FILES appropriately.
ERROR: core-image-minimal-1.0-r0 do_image_wic: Execution of '/home/vagrant/saman/meta-rauc-rpi/build/tmp/work/raspberrypi3-poky-linux-gnueabi/core-image-minimal/1.0-r0/temp/run.do_image_wic.2253626' failed with exit code 1
ERROR: Logfile of failure stored in: /home/vagrant/saman/meta-rauc-rpi/build/tmp/work/raspberrypi3-poky-linux-gnueabi/core-image-minimal/1.0-r0/temp/log.do_image_wic.2253626
ERROR: Task (/home/vagrant/saman/meta-rauc-rpi/meta/recipes-core/images/core-image-minimal.bb:do_image_wic) failed with exit code '1'
NOTE: Tasks Summary: Attempted 3520 tasks of which 8 didn't need to be rerun and 1 failed.

local.conf

# This file is your local configuration file and is where all local user settings
# are placed. The comments in this file give some guide to the options a new user
# to the system might want to change but pretty much any configuration option can
# be set in this file. More adventurous users can look at local.conf.extended
# which contains other examples of configuration which can be placed in this file
# but new users likely won't need any of them initially.
#
# Lines starting with the '#' character are commented out and in some cases the
# default values are provided as comments to show people example syntax. Enabling
# the option is a question of removing the # character and making any change to the
# variable as required.

#
# Machine Selection
#
# You need to select a specific machine to target the build with. There are a selection
# of emulated machines available which can boot and run in the QEMU emulator:
#
#MACHINE ?= "qemuarm"
#MACHINE ?= "qemuarm64"
#MACHINE ?= "qemumips"
#MACHINE ?= "qemumips64"
#MACHINE ?= "qemuppc"
#MACHINE ?= "qemux86"
#MACHINE ?= "qemux86-64"
#
# There are also the following hardware board target machines included for 
# demonstration purposes:
#
#MACHINE ?= "beaglebone-yocto"
#MACHINE ?= "genericx86"
#MACHINE ?= "genericx86-64"
#MACHINE ?= "mpc8315e-rdb"
#MACHINE ?= "edgerouter"
#
# This sets the default machine to be qemux86-64 if no other machine is selected:
MACHINE ??= "qemux86-64"

#
# Where to place downloads
#
# During a first build the system will download many different source code tarballs
# from various upstream projects. This can take a while, particularly if your network
# connection is slow. These are all stored in DL_DIR. When wiping and rebuilding you
# can preserve this directory to speed up this part of subsequent builds. This directory
# is safe to share between multiple builds on the same machine too.
#
# The default is a downloads directory under TOPDIR which is the build directory.
#
#DL_DIR ?= "${TOPDIR}/downloads"

#
# Where to place shared-state files
#
# BitBake has the capability to accelerate builds based on previously built output.
# This is done using "shared state" files which can be thought of as cache objects
# and this option determines where those files are placed.
#
# You can wipe out TMPDIR leaving this directory intact and the build would regenerate
# from these files if no changes were made to the configuration. If changes were made
# to the configuration, only shared state files where the state was still valid would
# be used (done using checksums).
#
# The default is a sstate-cache directory under TOPDIR.
#
#SSTATE_DIR ?= "${TOPDIR}/sstate-cache"

#
# Where to place the build output
#
# This option specifies where the bulk of the building work should be done and
# where BitBake should place its temporary files and output. Keep in mind that
# this includes the extraction and compilation of many applications and the toolchain
# which can use Gigabytes of hard disk space.
#
# The default is a tmp directory under TOPDIR.
#
#TMPDIR = "${TOPDIR}/tmp"

#
# Default policy config
#
# The distribution setting controls which policy settings are used as defaults.
# The default value is fine for general Yocto project use, at least initially.
# Ultimately when creating custom policy, people will likely end up subclassing 
# these defaults.
#
DISTRO ?= "poky"
# As an example of a subclass there is a "bleeding" edge policy configuration
# where many versions are set to the absolute latest code from the upstream 
# source control systems. This is just mentioned here as an example, its not
# useful to most new users.
# DISTRO ?= "poky-bleeding"

#
# Package Management configuration
#
# This variable lists which packaging formats to enable. Multiple package backends
# can be enabled at once and the first item listed in the variable will be used
# to generate the root filesystems.
# Options are:
#  - 'package_deb' for debian style deb files
#  - 'package_ipk' for ipk files are used by opkg (a debian style embedded package manager)
#  - 'package_rpm' for rpm style packages
# E.g.: PACKAGE_CLASSES ?= "package_rpm package_deb package_ipk"
# We default to rpm:
PACKAGE_CLASSES ?= "package_rpm"

#
# SDK target architecture
#
# This variable specifies the architecture to build SDK items for and means
# you can build the SDK packages for architectures other than the machine you are
# running the build on (i.e. building i686 packages on an x86_64 host).
# Supported values are i686 and x86_64
#SDKMACHINE ?= "i686"

#
# Extra image configuration defaults
#
# The EXTRA_IMAGE_FEATURES variable allows extra packages to be added to the generated
# images. Some of these options are added to certain image types automatically. The
# variable can contain the following options:
#  "dbg-pkgs"       - add -dbg packages for all installed packages
#                     (adds symbol information for debugging/profiling)
#  "src-pkgs"       - add -src packages for all installed packages
#                     (adds source code for debugging)
#  "dev-pkgs"       - add -dev packages for all installed packages
#                     (useful if you want to develop against libs in the image)
#  "ptest-pkgs"     - add -ptest packages for all ptest-enabled packages
#                     (useful if you want to run the package test suites)
#  "tools-sdk"      - add development tools (gcc, make, pkgconfig etc.)
#  "tools-debug"    - add debugging tools (gdb, strace)
#  "eclipse-debug"  - add Eclipse remote debugging support
#  "tools-profile"  - add profiling tools (oprofile, lttng, valgrind)
#  "tools-testapps" - add useful testing tools (ts_print, aplay, arecord etc.)
#  "debug-tweaks"   - make an image suitable for development
#                     e.g. ssh root access has a blank password
# There are other application targets that can be used here too, see
# meta/classes/image.bbclass and meta/classes/core-image.bbclass for more details.
# We default to enabling the debugging tweaks.
EXTRA_IMAGE_FEATURES ?= "debug-tweaks"

#
# Additional image features
#
# The following is a list of additional classes to use when building images which
# enable extra features. Some available options which can be included in this variable
# are:
#   - 'buildstats' collect build statistics
#   - 'image-mklibs' to reduce shared library files size for an image
#   - 'image-prelink' in order to prelink the filesystem image
# NOTE: if listing mklibs & prelink both, then make sure mklibs is before prelink
# NOTE: mklibs also needs to be explicitly enabled for a given image, see local.conf.extended
USER_CLASSES ?= "buildstats image-mklibs image-prelink"

#
# Runtime testing of images
#
# The build system can test booting virtual machine images under qemu (an emulator)
# after any root filesystems are created and run tests against those images. It can also
# run tests against any SDK that are built. To enable this uncomment these lines.
# See classes/test{image,sdk}.bbclass for further details.
#IMAGE_CLASSES += "testimage testsdk"
#TESTIMAGE_AUTO_qemuall = "1"

#
# Interactive shell configuration
#
# Under certain circumstances the system may need input from you and to do this it
# can launch an interactive shell. It needs to do this since the build is
# multithreaded and needs to be able to handle the case where more than one parallel
# process may require the user's attention. The default is iterate over the available
# terminal types to find one that works.
#
# Examples of the occasions this may happen are when resolving patches which cannot
# be applied, to use the devshell or the kernel menuconfig
#
# Supported values are auto, gnome, xfce, rxvt, screen, konsole (KDE 3.x only), none
# Note: currently, Konsole support only works for KDE 3.x due to the way
# newer Konsole versions behave
#OE_TERMINAL = "auto"
# By default disable interactive patch resolution (tasks will just fail instead):
PATCHRESOLVE = "noop"

#
# Disk Space Monitoring during the build
#
# Monitor the disk space during the build. If there is less that 1GB of space or less
# than 100K inodes in any key build location (TMPDIR, DL_DIR, SSTATE_DIR), gracefully
# shutdown the build. If there is less that 100MB or 1K inodes, perform a hard abort
# of the build. The reason for this is that running completely out of space can corrupt
# files and damages the build in ways which may not be easily recoverable.
# It's necesary to monitor /tmp, if there is no space left the build will fail
# with very exotic errors.
BB_DISKMON_DIRS ??= "\
    STOPTASKS,${TMPDIR},1G,100K \
    STOPTASKS,${DL_DIR},1G,100K \
    STOPTASKS,${SSTATE_DIR},1G,100K \
    STOPTASKS,/tmp,100M,100K \
    ABORT,${TMPDIR},100M,1K \
    ABORT,${DL_DIR},100M,1K \
    ABORT,${SSTATE_DIR},100M,1K \
    ABORT,/tmp,10M,1K"

#
# Shared-state files from other locations
#
# As mentioned above, shared state files are prebuilt cache data objects which can
# used to accelerate build time. This variable can be used to configure the system
# to search other mirror locations for these objects before it builds the data itself.
#
# This can be a filesystem directory, or a remote url such as http or ftp. These
# would contain the sstate-cache results from previous builds (possibly from other
# machines). This variable works like fetcher MIRRORS/PREMIRRORS and points to the
# cache locations to check for the shared objects.
# NOTE: if the mirror uses the same structure as SSTATE_DIR, you need to add PATH
# at the end as shown in the examples below. This will be substituted with the
# correct path within the directory structure.
#SSTATE_MIRRORS ?= "\
#file://.* http://someserver.tld/share/sstate/PATH;downloadfilename=PATH \n \
#file://.* file:///some/local/dir/sstate/PATH"

#
# Yocto Project SState Mirror
#
# The Yocto Project has prebuilt artefacts available for its releases, you can enable
# use of these by uncommenting the following line. This will mean the build uses
# the network to check for artefacts at the start of builds, which does slow it down
# equally, it will also speed up the builds by not having to build things if they are
# present in the cache. It assumes you can download something faster than you can build it
# which will depend on your network.
#
#SSTATE_MIRRORS ?= "file://.* http://sstate.yoctoproject.org/2.5/PATH;downloadfilename=PATH"

#
# Qemu configuration
#
# By default native qemu will build with a builtin VNC server where graphical output can be
# seen. The line below enables the SDL UI frontend too.
PACKAGECONFIG_append_pn-qemu-system-native = " sdl"
# By default libsdl2-native will be built, if you want to use your host's libSDL instead of 
# the minimal libsdl built by libsdl2-native then uncomment the ASSUME_PROVIDED line below.
#ASSUME_PROVIDED += "libsdl2-native"

# You can also enable the Gtk UI frontend, which takes somewhat longer to build, but adds
# a handy set of menus for controlling the emulator.
#PACKAGECONFIG_append_pn-qemu-system-native = " gtk+"

#
# Hash Equivalence
#
# Enable support for automatically running a local hash equivalence server and
# instruct bitbake to use a hash equivalence aware signature generator. Hash
# equivalence improves reuse of sstate by detecting when a given sstate
# artifact can be reused as equivalent, even if the current task hash doesn't
# match the one that generated the artifact.
#
# A shared hash equivalent server can be set with "<HOSTNAME>:<PORT>" format
#
#BB_HASHSERVE = "auto"
#BB_SIGNATURE_HANDLER = "OEEquivHash"

# CONF_VERSION is increased each time build/conf/ changes incompatibly and is used to
# track the version of this file when it was generated. This can safely be ignored if
# this doesn't mean anything to you.
CONF_VERSION = "1"

MACHINE = "raspberrypi4"

DISTRO_FEATURES_append = " systemd"
VIRTUAL-RUNTIME_init_manager = "systemd"
DISTRO_FEATURES_BACKFILL_CONSIDERED = "sysvinit"
VIRTUAL-RUNTIME_initscripts = ""

IMAGE_INSTALL_append = " rauc"

IMAGE_FSTYPES="tar.bz2 ext4 wic.bz2 wic.bmap"
SDIMG_ROOTFS_TYPE="ext4"
ENABLE_UART = "1"
RPI_USE_U_BOOT = "1"
PREFERRED_PROVIDER_virtual/bootloader = "u-boot"

WKS_FILE = "sdimage-dual-raspberrypi.wks"

leon-anavi · 2023-01-05T09:44:14Z

leon-anavi
Jan 5, 2023
Collaborator

Hi @samannazz,

Please WKS_FILE = "sdimage-dual-raspberrypi.wks.in" as noted in the README.rst of the master branch: https://github.com/rauc/meta-rauc-community/tree/master/meta-rauc-raspberrypi#ii-build-the-demo-system

At some point sdimage-dual-raspberrypi.wks was renamed to sdimage-dual-raspberrypi.wks.in and README.rst has been updated accordingly.

Best regards,
Leon

0 replies

samannazz · 2023-01-05T09:50:28Z

samannazz
Jan 5, 2023
Author

Alright, @leon-anavi, I think this blog is written by you:
https://www.konsulko.com/getting-started-with-rauc-on-raspberry-pi-2#:~:text=RAUC%20is%20a%20powerful%20and,in%20the%20Linux%20kernel%20configurations.

Here, WKS_FILE = "sdimage-dual-raspberrypi.wks" is written.

0 replies

leon-anavi · 2023-01-05T09:54:54Z

leon-anavi
Jan 5, 2023
Collaborator

Yes, good point, we need to correct it there. Thank you for reporting it.

Best regards,
Leon

0 replies

samannazz · 2023-01-08T19:17:57Z

samannazz
Jan 8, 2023
Author

@leon-anavi, I had build the image successfully and burn that image on sd-card by this command.
bzcat /path/to/core-image-minimal-raspberrypi3.wic.bz2 | dd of=/dev/sdb
then connected the Raspberry Pi to an external desktop screen, Ethernet, and power cable, but the system did not boot up.

0 replies

leon-anavi · 2023-01-08T19:20:55Z

leon-anavi
Jan 8, 2023
Collaborator

Hi @samannazz,

@leon-anavi, I had build the image successfully and burn that image on sd-card by this command. bzcat /path/to/core-image-minimal-raspberrypi3.wic.bz2 | dd of=/dev/sdb then connected the Raspberry Pi to an external desktop screen, Ethernet, and power cable, but the system did not boot up.

You have replaced /path/to/ with the actual path to the image, right?

Please have a look at the serial output to see what the problem is and share the log here.

Best regards,
Leon

0 replies

samannazz · 2023-01-09T09:15:38Z

samannazz
Jan 9, 2023
Author

Hi @leon-anavi,

Actually, I built the meta-rauc for rpi in a virtual machine (accessing the vm via vcn viewer). After building it, I copied the image core-image-minimal-raspberrypi3.wic.bz2 to my local host machine, burned it onto an sd card, and put that sd card into the rpi3. I also attached the serial cable and Ethernet. However, when I powered it on and ran "lsusb" on the terminal, it did not show my rpi.

I tested the rpi with another sd card that had ubuntu os burned onto it and it worked fine with the rpi.

So, it seems like there may be a problem with the core-image-minimal-raspberrypi3.wic.bz2 image.

0 replies

leon-anavi · 2023-01-09T09:18:46Z

leon-anavi
Jan 9, 2023
Collaborator

Hi @samannazz,

Sorry, we can't debug it without any boot logs. If you provide any logs from the serial output I will be able to give you guidelines for debugging this.

Best regards,
Leon

0 replies

samannazz · 2023-01-09T11:11:06Z

samannazz
Jan 9, 2023
Author

Hi @leon-anavi,
I tried to connect the ttl to the rpi uart using a serial connection, but for some reason I was unable to connect it.
On the other hand, I have a question. In local.conf, I specified

MACHINE = "raspberrypi3"
but after building, the image name shows that it was built for the rpi4.

2 replies

ejoerns Jan 9, 2023
Maintainer

Please run bitbake -e | grep "^MACHINE" to see what machine you are building for. This build was for rpi4, yes.

samannazz Jan 9, 2023
Author

Yes, ejoerns, it was built for the rpi4 by mistake.

leon-anavi · 2023-01-09T11:25:44Z

leon-anavi
Jan 9, 2023
Collaborator

@samannazz when you run bitbake core-image-minimal you will see Build Configuration: so make sure the correct machine is written there.

However, kindly please note that these are basic Yocto/OpenEmbedded questions not directly related to RAUC and I don't have the time to provide too much further assistance. Yocto has a steep learning curve and in my opinion you better have a very good understanding of it before proceeding with meta-rauc-community integrations.

Best regards, Leon

0 replies

samannazz · 2023-01-11T06:03:46Z

samannazz
Jan 11, 2023
Author

Hi @ejoerns, I have set up the meta-rauc for qemux86-64, and when I run the image:
runqemu nographic slirp ovmf wic core-image-minimal

i am following this https://www.pengutronix.de/en/blog/2022-02-03-tutorial-evaluating-rauc-on-qemu-a-quick-setup-with-yocto.html

the system boots up, but it fails to start the rauc update service.

12 replies

ejoerns Jan 11, 2023
Maintainer

Start with a clean environment then.

And since meta-rauc-qemux86 is tested (and compatible) with kirkstone, I would recommend using kirkstone first of all.

samannazz Jan 11, 2023
Author

@ejoerns, i have check the compatibility of layers with yocto, layers i have used:

git clone -b kirkstone https://git.yoctoproject.org/poky
git clone -b kirkstone https://github.com/rauc/meta-rauc.git
git clone -b master https://github.com/rauc/meta-rauc-community.git

i just want to make sure the compatibility before building the image.

ejoerns Jan 11, 2023
Maintainer

You have omitted the interesting part (traceback).

yocto-check-layer checks other things than the ones that are interesting for your build I guess.

samannazz Jan 11, 2023
Author

here is the full part:

vagrant@lana-gib-node:~/saman/rauc-qemu-demo/build$ yocto-check-layer ../meta-rauc
INFO: Detected layers:
INFO: meta-rauc: LayerType.SOFTWARE, /home/vagrant/saman/rauc-qemu-demo/meta-rauc
INFO: 
INFO: Setting up for meta-rauc(LayerType.SOFTWARE), /home/vagrant/saman/rauc-qemu-demo/meta-rauc
INFO: Getting initial bitbake variables ...
INFO: Getting initial signatures ...
INFO: Adding layer meta-rauc
INFO: Starting to analyze: meta-rauc
INFO: ----------------------------------------------------------------------
INFO: skipped "BSPCheckLayer: Layer meta-rauc isn't BSP one."
INFO: test_layerseries_compat (common.CommonCheckLayer)
INFO:  ... ok
INFO: test_parse (common.CommonCheckLayer)
INFO:  ... ok
INFO: test_readme (common.CommonCheckLayer)
INFO:  ... ok
INFO: test_show_environment (common.CommonCheckLayer)
INFO:  ... ok
INFO: test_signatures (common.CommonCheckLayer)
INFO:  ... ok
INFO: test_world (common.CommonCheckLayer)
INFO:  ... ERROR
INFO: Traceback (most recent call last):
  File "/home/vagrant/saman/rauc-qemu-demo/poky/scripts/lib/checklayer/cases/common.py", line 58, in test_world
    get_signatures(self.td['builddir'], failsafe=False)
  File "/home/vagrant/saman/rauc-qemu-demo/poky/scripts/lib/checklayer/__init__.py", line 315, in get_signatures
    check_command('Generating signatures failed. This might be due to some parse error and/or general layer incompatibilities.',
  File "/home/vagrant/saman/rauc-qemu-demo/poky/scripts/lib/checklayer/__init__.py", line 287, in check_command
    raise RuntimeError(msg)
RuntimeError: Generating signatures failed. This might be due to some parse error and/or general layer incompatibilities.
Command: BB_ENV_PASSTHROUGH_ADDITIONS="$BB_ENV_PASSTHROUGH_ADDITIONS BB_SIGNATURE_HANDLER" BB_SIGNATURE_HANDLER="OEBasicHash" bitbake -S none world
Output:
WARNING: You have included the meta-rauc layer, but 'rauc' has not been enabled in your DISTRO_FEATURES. See the meta-rauc README.rst for details on enabling RAUC support for your platform.
Loading cache...done.
Loaded 1657 entries from dependency cache.
NOTE: Resolving any missing task queue dependencies
ERROR: Nothing PROVIDES 'fuse' (but /home/vagrant/saman/rauc-qemu-demo/meta-rauc/recipes-casync/casync/casync_git.bb DEPENDS on or otherwise requires it)
ERROR: Required build target 'meta-world-pkgdata' has no buildable providers.
Missing or unbuildable dependency chain was: ['meta-world-pkgdata', 'casync', 'fuse']

Summary: There was 1 WARNING message.
Summary: There were 2 ERROR messages, returning a non-zero exit code.


INFO: test_world_inherit_class (common.CommonCheckLayer)
INFO:  ... FAIL
INFO: Traceback (most recent call last):
  File "/home/vagrant/saman/rauc-qemu-demo/poky/scripts/lib/checklayer/cases/common.py", line 73, in test_world_inherit_class
    self.fail('\n'.join(msg))
AssertionError: Layer meta-rauc failed additional checks from yocto-check-layer.bbclass
See below log for specific recipe parsing errors:

Generating signatures failed. This might be due to some parse error and/or general layer incompatibilities.
Command: BB_ENV_PASSTHROUGH_ADDITIONS="$BB_ENV_PASSTHROUGH_ADDITIONS BB_SIGNATURE_HANDLER" BB_SIGNATURE_HANDLER="OEBasicHash" BB_ENV_PASSTHROUGH_ADDITIONS="$BB_ENV_PASSTHROUGH_ADDITIONS INHERIT" INHERIT="yocto-check-layer" bitbake -S none world
Output:
WARNING: You have included the meta-rauc layer, but 'rauc' has not been enabled in your DISTRO_FEATURES. See the meta-rauc README.rst for details on enabling RAUC support for your platform.
Loading cache...done.
Loaded 0 entries from dependency cache.
Parsing recipes...done.
Parsing of 895 .bb files complete (0 cached, 895 parsed). 1657 targets, 44 skipped, 0 masked, 0 errors.
NOTE: Resolving any missing task queue dependencies
ERROR: Nothing PROVIDES 'fuse' (but /home/vagrant/saman/rauc-qemu-demo/meta-rauc/recipes-casync/casync/casync_git.bb DEPENDS on or otherwise requires it)
ERROR: Required build target 'meta-world-pkgdata' has no buildable providers.
Missing or unbuildable dependency chain was: ['meta-world-pkgdata', 'casync', 'fuse']

Summary: There was 1 WARNING message.
Summary: There were 2 ERROR messages, returning a non-zero exit code.


INFO: skipped "DistroCheckLayer: Layer meta-rauc isn't Distro one."
INFO: ======================================================================
INFO: ERROR: test_world (common.CommonCheckLayer)
INFO: ----------------------------------------------------------------------
INFO: Traceback (most recent call last):
  File "/home/vagrant/saman/rauc-qemu-demo/poky/scripts/lib/checklayer/cases/common.py", line 58, in test_world
    get_signatures(self.td['builddir'], failsafe=False)
  File "/home/vagrant/saman/rauc-qemu-demo/poky/scripts/lib/checklayer/__init__.py", line 315, in get_signatures
    check_command('Generating signatures failed. This might be due to some parse error and/or general layer incompatibilities.',
  File "/home/vagrant/saman/rauc-qemu-demo/poky/scripts/lib/checklayer/__init__.py", line 287, in check_command
    raise RuntimeError(msg)
RuntimeError: Generating signatures failed. This might be due to some parse error and/or general layer incompatibilities.
Command: BB_ENV_PASSTHROUGH_ADDITIONS="$BB_ENV_PASSTHROUGH_ADDITIONS BB_SIGNATURE_HANDLER" BB_SIGNATURE_HANDLER="OEBasicHash" bitbake -S none world
Output:
WARNING: You have included the meta-rauc layer, but 'rauc' has not been enabled in your DISTRO_FEATURES. See the meta-rauc README.rst for details on enabling RAUC support for your platform.
Loading cache...done.
Loaded 1657 entries from dependency cache.
NOTE: Resolving any missing task queue dependencies
ERROR: Nothing PROVIDES 'fuse' (but /home/vagrant/saman/rauc-qemu-demo/meta-rauc/recipes-casync/casync/casync_git.bb DEPENDS on or otherwise requires it)
ERROR: Required build target 'meta-world-pkgdata' has no buildable providers.
Missing or unbuildable dependency chain was: ['meta-world-pkgdata', 'casync', 'fuse']

Summary: There was 1 WARNING message.
Summary: There were 2 ERROR messages, returning a non-zero exit code.

======================================================================
INFO: FAIL: test_world_inherit_class (common.CommonCheckLayer)
INFO: ----------------------------------------------------------------------
INFO: Traceback (most recent call last):
  File "/home/vagrant/saman/rauc-qemu-demo/poky/scripts/lib/checklayer/cases/common.py", line 73, in test_world_inherit_class
    self.fail('\n'.join(msg))
AssertionError: Layer meta-rauc failed additional checks from yocto-check-layer.bbclass
See below log for specific recipe parsing errors:

Generating signatures failed. This might be due to some parse error and/or general layer incompatibilities.
Command: BB_ENV_PASSTHROUGH_ADDITIONS="$BB_ENV_PASSTHROUGH_ADDITIONS BB_SIGNATURE_HANDLER" BB_SIGNATURE_HANDLER="OEBasicHash" BB_ENV_PASSTHROUGH_ADDITIONS="$BB_ENV_PASSTHROUGH_ADDITIONS INHERIT" INHERIT="yocto-check-layer" bitbake -S none world
Output:
WARNING: You have included the meta-rauc layer, but 'rauc' has not been enabled in your DISTRO_FEATURES. See the meta-rauc README.rst for details on enabling RAUC support for your platform.
Loading cache...done.
Loaded 0 entries from dependency cache.
Parsing recipes...done.
Parsing of 895 .bb files complete (0 cached, 895 parsed). 1657 targets, 44 skipped, 0 masked, 0 errors.
NOTE: Resolving any missing task queue dependencies
ERROR: Nothing PROVIDES 'fuse' (but /home/vagrant/saman/rauc-qemu-demo/meta-rauc/recipes-casync/casync/casync_git.bb DEPENDS on or otherwise requires it)
ERROR: Required build target 'meta-world-pkgdata' has no buildable providers.
Missing or unbuildable dependency chain was: ['meta-world-pkgdata', 'casync', 'fuse']

Summary: There was 1 WARNING message.
Summary: There were 2 ERROR messages, returning a non-zero exit code.

----------------------------------------------------------------------
INFO: Ran 7 tests in 205.963s
INFO: FAILED
INFO:  (failures=1, errors=1, skipped=2)
INFO: 
INFO: Summary of results:
INFO: 
INFO: meta-rauc ... FAIL

ejoerns Jan 11, 2023
Maintainer

Thx. A world build builds casync, too and this requires meta-filesystem to be added (which provides fuse package).

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

do_image_wic: No kickstart files from WKS_FILES were found: sdimage-dual-raspberrypi.wks #50

{{title}}

Replies: 10 comments 14 replies

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

Select a reply

do_image_wic: No kickstart files from WKS_FILES were found: sdimage-dual-raspberrypi.wks #50

samannazz Jan 5, 2023

Replies: 10 comments · 14 replies

leon-anavi Jan 5, 2023 Collaborator

samannazz Jan 5, 2023 Author

leon-anavi Jan 5, 2023 Collaborator

samannazz Jan 8, 2023 Author

leon-anavi Jan 8, 2023 Collaborator

samannazz Jan 9, 2023 Author

leon-anavi Jan 9, 2023 Collaborator

samannazz Jan 9, 2023 Author

ejoerns Jan 9, 2023 Maintainer

samannazz Jan 9, 2023 Author

leon-anavi Jan 9, 2023 Collaborator

samannazz Jan 11, 2023 Author

ejoerns Jan 11, 2023 Maintainer

samannazz Jan 11, 2023 Author

ejoerns Jan 11, 2023 Maintainer

samannazz Jan 11, 2023 Author

ejoerns Jan 11, 2023 Maintainer

samannazz
Jan 5, 2023

Replies: 10 comments 14 replies

leon-anavi
Jan 5, 2023
Collaborator

samannazz
Jan 5, 2023
Author

leon-anavi
Jan 5, 2023
Collaborator

samannazz
Jan 8, 2023
Author

leon-anavi
Jan 8, 2023
Collaborator

samannazz
Jan 9, 2023
Author

leon-anavi
Jan 9, 2023
Collaborator

samannazz
Jan 9, 2023
Author

ejoerns Jan 9, 2023
Maintainer

samannazz Jan 9, 2023
Author

leon-anavi
Jan 9, 2023
Collaborator

samannazz
Jan 11, 2023
Author

ejoerns Jan 11, 2023
Maintainer

samannazz Jan 11, 2023
Author

ejoerns Jan 11, 2023
Maintainer

samannazz Jan 11, 2023
Author

ejoerns Jan 11, 2023
Maintainer