Created attachment 580 [details] fail log file [Environment] MACHINE = qemux86 DISTRO = "poky" PACKAGE_CLASSES = "package_ipk" Tree/Branch: Poky/Master Commit: 5ed855d12cddf2de535c3f6d05d3dfe85d69d99d Even though the building of core-image-sato-sdk didn't report any errors, lots of -dev packages are not installed in the final image.
Maybe a dup of 2598
*** Bug 2598 has been marked as a duplicate of this bug. ***
This is caused by us using the list of packages to install rather than the list of packages that have been installed in order to produce the list of dev/dbg packages to install; the list might not be complete due to dependencies installed by the package manager. This needs to be handled in a similar way to locales.
Is this a ipkg-specific issue?
No, it affects all packaging backends.
(In reply to comment #3) > This is caused by us using the list of packages to install rather than the > list of packages that have been installed in order to produce the list of > dev/dbg packages to install; the list might not be complete due to > dependencies installed by the package manager. This needs to be handled in a > similar way to locales. Why it was ok in 1.2 release? I don't recall anything changed here about the way how -dev packages get installed since 1.2.
Hmm, seems I was on the wrong track. We do have a problem with not all of the -dev packages being installed for all of the packages in the rootfs, and it is not specific to any backend, but that is a separate issue. The issue reported in this bug *is* ipk-specific - it seems that the dependencies between -dev packages when they are produced as ipks are missing and because of the other issue I mentioned above, they do not get pulled into the rootfs anymore.
The opkg-specific bug appears to have been caused by http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=e3a5089dbb843d013a2f1bb693312b86c717153b (I also replied with the info below to the mailing list thread for this patch.) This commit moved the config file to /etc/opkg, and opkg always reads all files under this directory even if -f is specified (as it is during do_rootfs in order to specify our own generated config file), and this means that after opkg-collateral is installed into the rootfs, this version of the config is used, resulting in opkg ignoring the list of packages it has already downloaded (since it now sees list_dir as var/lib/opkg instead of var/lib/opkg/lists) and thus it fails to install any of the "attemptonly" packages (including *-dev, *-dbg, etc.). The question is, should opkg be fixed to not load anything from etc/opkg/ when -f is specified?
Let's keep this bug concentrated on the opkg issue alone, which is now fixed in master revision 06348fe76474a20e0fc2f2938919f782c3e5ae28; accordingly I've removed the bug relationships since this issue is self-contained.
The "Unknown packages" messages in in log_do.rootfs disappeared, although there are several packages not installed: 'task-core-console-dev'. 'task-core-standalone-sdk-target-dev'. 'task-core-qt-dev'. 'task-core-x11-dev'. 'task-core-ssh-dropbear-dev'.
Reopening this as there is no error message or warning for not installing some of the packages on the INSTALL_PACKAGES_ATTEMPTONLY_IPK list. Resetting importance to minor
Are those packages you list actually included in INSTALL_PACKAGES_ATTEMPTONLY_IPK?
Yes. They are included I will attach the log.
Created attachment 658 [details] do_rootfs log
These packages genuinely do not exist, so it's expected that they cannot be installed. I suspect you will find after my rootfs patch series we won't even be attempting to install them since that introduces a check to see if the package is valid first.
Can we mark this as fixed again? AFAICT there is no issue here.
Marking as resolved again; if there is still an issue with do_rootfs taking the above comments into account, please reopen.
Setting this to verified after the latest comments
verified