Hoi
>
> This still fails on the autobuilders, I'm pretty sure the config for the
> build folder has:
> PACKAGE_CLASSES = "package_rpm"
>
aha! that is the missing puzzle piece - thanks!
thought i read somewhere that ipk is the default and geared the tests towards
that... "always check yous
Hello,
This still fails on the autobuilders, I'm pretty sure the config for the
build folder has:
PACKAGE_CLASSES = "package_rpm"
This explains this:
build-st-4166614$ tree tmp/deploy/images/qemux86-64/var/lib/
tmp/deploy/images/qemux86-64/var/lib/
├── dnf
│ ├── history.sqlite
│ ├──
systemd-sysext allows to overlay another image (or multiple) ontop of
a "base-image" = the current rootfs, via the use of overlayfs; to add
tools and features meant for development purposes.
To quote the documentation on systemd-sysext:
" ...addition in order to make debugging/development
ests passed (successes=1, skipped=0, failures=0, errors=0)
From: Alexandre Belloni
Sent: Sunday, April 21, 2024 22:36
To: SCHNEIDER Johannes
Cc: openembedded-core@lists.openembedded.org;
richard.pur...@linuxfoundation.org; alex.kana...@gmail.com
Subject:
On 15/04/2024 08:02:00+0200, Johannes Schneider via lists.openembedded.org
wrote:
> systemd-sysext allows to overlay another image (or multiple) ontop of
> a "base-image" = the current rootfs, via the use of overlayfs; to add
> tools and features meant for development purposes.
>
> To quote the
systemd-sysext allows to overlay another image (or multiple) ontop of
a "base-image" = the current rootfs, via the use of overlayfs; to add
tools and features meant for development purposes.
To quote the documentation on systemd-sysext:
" ...addition in order to make debugging/development
