Integrating prebuilt debian packages

Hi,

has anyone been able to integrate a debian package (program.deb) into the image-build-process and would like to present an example? I am stuck trying to add a very simple debian file. And it just won't work.

The Idea was from here: prebuilt-deb

I also expect that I will need the dpkg-prebuilt.bbclass

But after 10 builds or so i haven't gotten any further.

Thanks for your help

 This is what happens at the end of the build process:

DEBUG: Executing python function do_rootfs_install
DEBUG: Executing shell function root_cleandirs
DEBUG: Shell function root_cleandirs finished
DEBUG: Executing shell function rootfs_prepare
DEBUG: Shell function rootfs_prepare finished
DEBUG: Executing shell function rootfs_configure_isar_apt
DEBUG: Shell function rootfs_configure_isar_apt finished
DEBUG: Executing shell function image_configure_accounts
Do not execute usermod (no changes).
DEBUG: Shell function image_configure_accounts finished
DEBUG: Executing shell function image_configure_fstab
# Begin /etc/fstab
/dev/root    /        auto        defaults        0    0
proc        /proc        proc        nosuid,noexec,nodev    0    0
sysfs        /sys        sysfs        nosuid,noexec,nodev    0    0
devpts        /dev/pts    devpts        gid=5,mode=620        0    0
tmpfs        /run        tmpfs        defaults        0    0
devtmpfs    /dev        devtmpfs    mode=0755,nosuid    0    0

# End /etc/fstab
DEBUG: Shell function image_configure_fstab finished
DEBUG: Executing shell function rootfs_do_mounts
DEBUG: Shell function rootfs_do_mounts finished
DEBUG: Executing shell function rootfs_install_pkgs_update
Get:1 file:/isar-apt isar InRelease
Ign:1 file:/isar-apt isar InRelease
Get:2 file:/isar-apt isar Release [5087 B]
Get:2 file:/isar-apt isar Release [5087 B]
Get:3 file:/isar-apt isar Release.gpg
Ign:3 file:/isar-apt isar Release.gpg
Get:4 file:/isar-apt isar/main arm64 Packages [7189 B]
Reading package lists...
DEBUG: Shell function rootfs_install_pkgs_update finished
DEBUG: Executing shell function rootfs_install_resolvconf
DEBUG: Shell function rootfs_install_resolvconf finished
DEBUG: Executing shell function rootfs_import_package_cache
DEBUG: Shell function rootfs_import_package_cache finished
DEBUG: Executing shell function rootfs_install_pkgs_download
Reading package lists...
Building dependency tree...
Reading state information...
E: Unable to locate package prebuilt-deb
WARNING: exit code 100 from a shell command.
ERROR: Error executing a python function in exec_python_func() autogenerated:

The stack trace of python calls that resulted in this exception/failure was:
File: 'exec_python_func() autogenerated', lineno: 2, function: <module>
0001:
*** 0002:do_rootfs_install(d)
0003:
File: '/work/isar/meta/classes/rootfs.bbclass', lineno: 182, function: do_rootfs_install
0178:                                     shared=True)
0179:
0180:        bb.build.exec_func(cmd, d)
0181:
*** 0182:        if (d.getVarFlag(cmd, 'isar-apt-lock') or "") == "release-after":
0183:            bb.utils.unlockfile(lock)
0184:    progress_reporter.finish()
0185:}
0186:addtask rootfs_install before do_rootfs_postprocess after do_unpack
File: '/work/isar/bitbake/lib/bb/build.py', lineno: 251, function: exec_func
0247:    with bb.utils.fileslocked(lockfiles):
0248:        if ispython:
0249:            exec_func_python(func, d, runfile, cwd=adir)
0250:        else:
*** 0251:            exec_func_shell(func, d, runfile, cwd=adir)
0252:
0253:    try:
0254:        curcwd = os.getcwd()
0255:    except:
File: '/work/isar/bitbake/lib/bb/build.py', lineno: 452, function: exec_func_shell
0448:    with open(fifopath, 'r+b', buffering=0) as fifo:
0449:        try:
0450:            bb.debug(2, "Executing shell function %s" % func)
0451:            with open(os.devnull, 'r+') as stdin, logfile:
*** 0452:                bb.process.run(cmd, shell=False, stdin=stdin, log=logfile, extrafiles=[(fifo,readfifo)])
0453:        finally:
0454:            os.unlink(fifopath)
0455:
0456:    bb.debug(2, "Shell function %s finished" % func)
File: '/work/isar/bitbake/lib/bb/process.py', lineno: 182, function: run
0178:        if not stderr is None:
0179:            stderr = stderr.decode("utf-8")
0180:
0181:    if pipe.returncode != 0:
*** 0182:        raise ExecutionError(cmd, pipe.returncode, stdout, stderr)
0183:    return stdout, stderr
Exception: bb.process.ExecutionError: Execution of '/build/tmp/work/iot2050-debian-arm64/iot2050-image-example-iot2050-wic-img/1.0-r0/temp/run.rootfs_install_pkgs_download.285833' failed with exit code 100:
Reading package lists...
Building dependency tree...
Reading state information...
E: Unable to locate package prebuilt-deb
WARNING: exit code 100 from a shell command.


DEBUG: Python function do_rootfs_install finished

 I used the directory prebuilt-deb so that anyone can try the same. After copying it to the recipes-app directory and adding the line to the image rule of the example image (I only removed node-red and tcf-agent and tested this setup beforehand / didn't want to re-add it just for this test)...

IMAGE_INSTALL += " \
expand-on-first-boot \
sshd-regen-keys \
regen-rootfs-uuid \
install-on-emmc \
customizations-example \
switchserialmode \
iot2050setup \
iot2050-firmware-update \
mraa \
prebuilt-deb \
"

...I would then start the build process with the standard command

./kas-container build kas-iot2050-example.yml

TLDR:

IMAGE_INSTALL += "example-prebuilt"

There are two dependency levels with Isar. One is the normal Debian package level, and that is what IMAGE_INSTALL communicates to the rootfs assembly. The other is the bitbake recipe level. And that is what IMAGE_INSTALL uses to ensure that the recipe providing the binary package is built. If that recipe uses a different name for itself than for its package or if it generates multiple binary packages, it has to extend PROVIDES so that asking for the binary package will also trigger the recipe build. And that happens in this Isar example: binary package and recipe names are different, but recipe declares to provide the binary package explicitly.

Great, that did it!! Thank you.
Next thing will be for me to try out how well it works with multiple packages and also with more complex ones.

I am building the packages with fpm ( installation  getting-started ) from self compiled binaries.
Using Deb files gives me the advantage, that I can test the programs and their individual setups before even integrating them into the image build process.