binutils-symlinks is only an alias to the main package according to binutils.inc: RPROVIDES_${PN} += "${PN}-symlinks" I didn't write either of the tests, but yes - I can work on this tomorrow. Alex

Previously it was pulled in implicitly via poky default config. Signed-off-by: Alexander Kanavin <alex.kanavin@...> --- config.json | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff

Yocto does not provide a gcc that targets the host machine, only the cross gcc, whose output is unsuitable for running at configuration step. Meson assigns different meanings to these, yocto's host is

You probably need to adjust meson.cross which is written out by meson.bbclass. Alex

DEPENDS adds the dependencies into $WORKDIR/recipe-sysroot, and native pkg-config looks there for .pc files in that directory. Alex

You need to add DEPENDS = "libmnl" maybe? RDEPENDS is needed for runtime things like script interpreters or supplementary data; plain library dependencies are build-time. Alex

Thanks, I have added this to AUH repo too now; I assume there are no changes in the re-sent patchset otherwise? Alex

Can you please also send a patch to update http://git.yoctoproject.org/cgit/cgit.cgi/yocto-autobuilder-helper/tree/scripts/run-auh#n25 ? Then I can take this patch. I will add the first four patches n

Right, I agree with that. Then the patch is fine, but please send it to the correct list: openembedded-core@... Alex

Virgl is not verified with anything else than mesa, and will almost certainly fail. And so does qemu. I think you should rather remove glx and virglrenderer from qemu PACKAGECONFIG, so that mesa is no

You need to look into what the postinst_ontarget actually does, and why can it only happen on target. Or do not use a readonly rootfs. Alex

#yocto

You can try to list the process tree with ps axjf, and the innermost under do_install is probably the one that is stuck. Then you can attach gdb to it to see what it is doing. Alex

It goes over a list of packages installed into their image, and checks their licensing. If something was directly built into something else, it will not produce a separate package, and therefore you n

On master, you can set INCOMPATIBLE_LICENSE in the image recipe, rather than globally, then the check would only be performed on items that actually go into that image. Warrior does not have that feat

Sadly, many maintainers do not act on AUH mails in a timely manner (or do not act at all). Sending these emails to oe-core list as well will allow other people to pick them up, and ease up the path to

Previously it was same as status update recipients. Signed-off-by: Alexander Kanavin <alex.kanavin@...> --- upgrade-helper.conf | 3 +++ upgradehelper.py | 4 ++-- 2 files changed, 5 insertions(+)

Signed-off-by: Alexander Kanavin <alex.kanavin@...> --- modules/utils/emailhandler.py | 2 ++ 1 file changed, 2 insertions(+) diff --git a/modules/utils/emailhandler.py b/modules/utils/emailhandl

Not only that, the only reason ruby is in core at all is that webkit needs ruby-native. The interest in it is simply too low, but of course automated tests are welcome. Alex

What about half-installed packages? Does dpkg guarantee atomicity on that level, and if so, how? The situation where the system boots with a core package being a mix of old and upgraded version isn't

Right. Where I work, the updates would be performed through an A/B partition scheme: if the update is botched, it is always possible to roll back. This doubles the disk space requirement, but is far m