Yes, it's worth. Thanks

never mind, just took a look at the commit which does exactly this. is it worth submitting a patch to tweak the few hard assignments? rday

i just now determined that that is exactly what is happening -- tried it with nanopb recipe from meta-oe, which contains: PNBLACKLIST[nanopb] = "Needs forward porting to use python3" switched

Yes, in local.conf or distro config, both work fine. Maybe your PNBLACKLIST you're trying to unblacklist is using normal assignment instead of weak one?

*where* did you set it to empty? in your local.conf?

i tested it ... at least i *thought* i tested it on a blacklisted recipe. i'll try it again, i guess i just misspelled something. rday

I don't use WR, but setting it to empty works fine for me. Why do you think it shouldn't work? See https://git.openembedded.org/openembedded-core/tree/meta/classes/blacklist.bbclass#n18

asking what is almost certainly a silly question, but as i'm poring over the wind river LTS 19 (aka "zeus") developer's guide, i know that WR adds a feature for un-blacklisting blacklisted recipes via

FWIW, you could make the parsing order not matter (at least in thud, from a quick look, master as well). LAYERSERIES_COMPAT is resolved after all layer.conf have been parsed[1]. I do not know if it's

Hi, I'm using this command from a new image type ''' gpg --homedir home --encrypt --sign --default-key "server@..." --pinentry-mode loopback --passphrase-file server.passphrase --recipient

Please unsubscribe me from the mailing list.

You can add a layer which will set LAYERSERIES_COMPAT for another layer, but it needs to be parsed before the layer you want to change,

Hi, have an issue with a layer which doesn't have the current dunfell release in it's LAYERSERIES_COMPAT_ -> can I overwrite it somehow in a different layer or local.conf? -> can I configure the error

i suspected it was a WR thing, thanks. rday

Is it possible to continue to add ptest for python-XX in the old way at present, and wait for the new recipe to be integrated (uncertain time), and then uniformly process the output? Or suspend the

I like the idea of format the output at level of pytest, in OEQA there is OETestResult class that is where the changes need to be made to add the option to use AM

To me this seems like Wind River's special sauce. The CHANGELOG in meta-intel says this: Added QEMU support. ------------------- We now build several virtio drivers into the kernel by default,

currently poring over wind river docs and in release notes for WR LTS 19 (equivalent to YP 3.0), one of the notes for RCPL 7 for this release of WR states: "New support to deploy a platform project

Hi, I am cross compile nodejs 12.16 recipe for ARM v7 target using Yocto 2.2. I can built nodejs as a individual task (i.e. bitbake -c compile) (with some changes in recipe) with dependency over

Op 03-05-2020 om 13:42 schreef Gmane Admin: Self answering, I added this to my image recipe: ROOTFS_POSTPROCESS_COMMAND += "install_initrd; " install_initrd() { bbnote "Adding initrd to image