* Why was package not included in my image despite of being a runtime dependency of one which was included?
@ 2023-12-05 22:27 Kuba Sanak
2023-12-06 9:46 ` [yocto] " Alexander Kanavin
0 siblings, 1 reply; 2+ messages in thread
From: Kuba Sanak @ 2023-12-05 22:27 UTC (permalink / raw)
To: yocto
I'm building a systemd-based image with Yocto I've run into a problem where update-rc.d (which is needed by a systemd sysv wrapper) is not present in that image.
I can confirm that update-rc.d is listed as a runtime dependency of systemd:
$ bitbake systemd -e | grep "^RDEPENDS"
RDEPENDS:systemd=" kmod dbus util-linux-mount util-linux-umount udev (= 1:250.4-r0) systemd-udev-rules util-linux-agetty util-linux-fsck systemd-serialgetty volatile-binds ldconfig libnss-myhostname pam-plugin-unix pam-plugin-loginuid pam-plugin-keyinit systemd-compat-units update-rc.d systemd-vconsole-setup"
RDEPENDS:systemd-bash-completion="bash-completion"
RDEPENDS:systemd-conf=" update-rc.d"
RDEPENDS:systemd-dev="systemd (= 1:250.4-r0)"
RDEPENDS:systemd-doc=" "
RDEPENDS:systemd-initramfs="systemd"
RDEPENDS:systemd-kernel-install=" bash"
RDEPENDS:systemd-staticdev="systemd-dev (= 1:250.4-r0)"
RDEPENDS:udev-hwdb=" udev"
And systemd is obviously included in my image because I can see it working. Also inspecting my image manifest confirms that systemd has been included in the image.
$ grep -n systemd tmp/deploy/images/<arch>/<image_name>.manifest
283:libsystemd-shared cortexa55 1:250.4-r0
284:libsystemd0 cortexa55 1:250.4-r0
394:systemd cortexa55 1:250.4-r0
395:systemd-compat-units cortexa55 1.0-r29
396:systemd-conf txrz_g2l0 1:1.0-r0
397:systemd-extra-utils cortexa55 1:250.4-r0
398:systemd-serialgetty txrz_g2l0 1.0-r5
399:systemd-udev-rules cortexa55 1:250.4-r0
400:systemd-vconsole-setup cortexa55 1:250.4-r0
And yet, update-rc.d keeps not being included in the resultant image. The package name (i.e. update-rc.d) is missing from the manifest and the actual script file it's supposed to provide is missing from the image rootfs.
Why is this happening and what can I do to debug why this runtime dependency is missing?
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [yocto] Why was package not included in my image despite of being a runtime dependency of one which was included?
2023-12-05 22:27 Why was package not included in my image despite of being a runtime dependency of one which was included? Kuba Sanak
@ 2023-12-06 9:46 ` Alexander Kanavin
0 siblings, 0 replies; 2+ messages in thread
From: Alexander Kanavin @ 2023-12-06 9:46 UTC (permalink / raw)
To: contact; +Cc: yocto
You should look at log.do_rootfs for your image (in $WORKDIR under
temp/) to see what is happening at the actual package transaction.
Also, find the package which should pull in the one that's missing (in
tmp/deploy for example), and inspect that it does indeed contain the
dependency.
Alex
On Tue, 5 Dec 2023 at 23:27, Kuba Sanak via lists.yoctoproject.org
<contact=kuba.fyi@lists.yoctoproject.org> wrote:
>
> I'm building a systemd-based image with Yocto I've run into a problem where update-rc.d (which is needed by a systemd sysv wrapper) is not present in that image.
>
> I can confirm that update-rc.d is listed as a runtime dependency of systemd:
>
> $ bitbake systemd -e | grep "^RDEPENDS"
> RDEPENDS:systemd=" kmod dbus util-linux-mount util-linux-umount udev (= 1:250.4-r0) systemd-udev-rules util-linux-agetty util-linux-fsck systemd-serialgetty volatile-binds ldconfig libnss-myhostname pam-plugin-unix pam-plugin-loginuid pam-plugin-keyinit systemd-compat-units update-rc.d systemd-vconsole-setup"
> RDEPENDS:systemd-bash-completion="bash-completion"
> RDEPENDS:systemd-conf=" update-rc.d"
> RDEPENDS:systemd-dev="systemd (= 1:250.4-r0)"
> RDEPENDS:systemd-doc=" "
> RDEPENDS:systemd-initramfs="systemd"
> RDEPENDS:systemd-kernel-install=" bash"
> RDEPENDS:systemd-staticdev="systemd-dev (= 1:250.4-r0)"
> RDEPENDS:udev-hwdb=" udev"
>
> And systemd is obviously included in my image because I can see it working. Also inspecting my image manifest confirms that systemd has been included in the image.
>
> $ grep -n systemd tmp/deploy/images/<arch>/<image_name>.manifest
> 283:libsystemd-shared cortexa55 1:250.4-r0
> 284:libsystemd0 cortexa55 1:250.4-r0
> 394:systemd cortexa55 1:250.4-r0
> 395:systemd-compat-units cortexa55 1.0-r29
> 396:systemd-conf txrz_g2l0 1:1.0-r0
> 397:systemd-extra-utils cortexa55 1:250.4-r0
> 398:systemd-serialgetty txrz_g2l0 1.0-r5
> 399:systemd-udev-rules cortexa55 1:250.4-r0
> 400:systemd-vconsole-setup cortexa55 1:250.4-r0
>
> And yet, update-rc.d keeps not being included in the resultant image. The package name (i.e. update-rc.d) is missing from the manifest and the actual script file it's supposed to provide is missing from the image rootfs.
>
> Why is this happening and what can I do to debug why this runtime dependency is missing?
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#61809): https://lists.yoctoproject.org/g/yocto/message/61809
> Mute This Topic: https://lists.yoctoproject.org/mt/103002275/1686489
> Group Owner: yocto+owner@lists.yoctoproject.org
> Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [alex.kanavin@gmail.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2023-12-06 9:46 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2023-12-05 22:27 Why was package not included in my image despite of being a runtime dependency of one which was included? Kuba Sanak
2023-12-06 9:46 ` [yocto] " Alexander Kanavin
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.