**** BEGIN LOGGING AT Sun Aug 18 02:59:57 2019 Aug 18 17:52:18 Can I remove all qemu packages from an image? I get "The postinstall intercept hook 'update_gio_module_cache' failed" with output: "[ True = False -a qemuwrapper-cross != nativesdk-qemuwrapper-cross ]" Aug 18 19:13:01 kayterina: qemu is not installed unless you actually ask for it. probably you are confusing qemu in the image with qemu on the host used for cross-architecture install tricks. **** BEGIN LOGGING AT Sun Aug 18 22:17:39 2019 Aug 18 22:39:09 New news from stackoverflow: What does runqemu script? Aug 19 01:34:39 Hi, does anyone know how to retrieve the version of another recipe using Bitbake? I've got some recipes on AUTOREV and so I'd like to add the PV of a recipe into the IMAGE_BUILDINFO_VARS so the revision that gets used, is recorded in the /etc/build file. Aug 19 01:36:55 I've tried using PV_pn-myrecipe but it's blank. If it helps, the IMAGE_BUILDINFO_VARS uses d.getVar() to fetch the value of each variable Aug 19 01:52:00 justinsg: not possible directly. recipes can't access the metadata of other recipes by design. indirectly it can be done. but it's probably better to use the image manifest. iirc there's an option to include it in the image Aug 19 02:01:47 kergoth: thanks, I figured that might be the case. I think the image manifest might be the way to go, although I can only see an option to install the license manifest (COPY_LIC_MANIFEST). Supposedly the image manifest can be installed using an IMAGE_PREPROCESS_COMMAND, but I'll have to dig a bit more to figure that out. How nasty is the indirect method? Aug 19 02:23:19 you could use pkgdata. all recipes in *this* build emit pkgdata, which are just text files with the info used to create the binary packages. we have functions for reading the data in Aug 19 02:23:53 your task would have to depend on do_package of all the dependent recipes Aug 19 02:25:09 couldn't append to IMAGE_BUILDINFO_VARS, as one task can;'t affect the metadata of another. you could use an IMAGE_PREPROCESS_COMMAND for that method as well ast he manifest method, actually Aug 19 02:25:33 still somewhat ugly, but workable Aug 19 02:29:47 kergoth: oh I see - somewhat ugly indeed. I took a look at the code that generates the image manifest, and I think oe.rootfs.image_list_installed_packages() is probably what I'm after. I can filter that a bit to create a mini manifest of the packages I specify. If I do that in a IMAGE_PREPROCESS_COMMAND task, I can probably just append /etc/build (provided I can ensure my task runs after the buildinfo Aug 19 02:29:47 IMAGE_PREPROCESS_COMMAND) Aug 19 02:30:26 ah, indeed, that presumably queries the package manager rather than poking around bitbake packaging internals Aug 19 02:30:34 that sounds better Aug 19 02:30:54 kergoth: hopefully :) thanks for your help! Aug 19 02:31:02 np, good luck with it **** ENDING LOGGING AT Mon Aug 19 02:59:57 2019