This is the result of automated script (0.9.0) conversion: oe-core/scripts/contrib/convert-overrides.py . converting the metadata to use ":" as the override character instead of "_". Signed-off-by: Ma

This is the result of automated script (0.9.0) conversion: oe-core/scripts/contrib/convert-overrides.py . converting the metadata to use ":" as the override character instead of "_". Signed-off-by: Ma

This marks the layers as compatible with honister now they use the new override syntax. Signed-off-by: Martin Jansa <Martin.Jansa@...> --- meta-filesystems/conf/layer.conf | 2 +- meta-gnome/conf

Would it make sense to replace shebang in such scripts to explicitly call python3? As it's not only the u-a for the python symlink, but RDEPENDS of the package should pull the right interpreter as wel

As this wasn't needed until now and python3 also doesn't use u-a for ${bindir}/python as all python3 scripts should explicitly call python3, why do you think it would be worth adding to dead python2 r

* to allow both python-chardet and python3-chardet to be installed in the same image * now it fails with: Collected errors: * check_data_file_clashes: Package python-chardet wants to install file imag

* introduced in libmediaart-2.0 with: https://git.openembedded.org/meta-openembedded/commit/?id=2b90058c346a5a56dced3c1b7413068027a884f1 Signed-off-by: Martin Jansa <Martin.Jansa@...> --- meta-m

* introduced in libmediaart-2.0 with: https://git.openembedded.org/meta-openembedded/commit/?id=2b90058c346a5a56dced3c1b7413068027a884f1 Signed-off-by: Martin Jansa <Martin.Jansa@...> --- meta-m

Hi, rygel and packagegroup-meta-multimedia.bb should be updated to respect gobject-introspection-data restriction, now world builds are failing with: ERROR: Nothing PROVIDES 'libmediaart-2.0' (but met

Backport the commit from master instead: https://git.openembedded.org/meta-openembedded/commit/?id=c7b77535e0b08e8c89f41fa0508d3b275c95ab80 in this case it's the same, but using the same commit messag

Backport the commit from master instead: https://git.openembedded.org/meta-openembedded/commit/?id=4ff5b43edd3dd5843d29b66d809cb5365e9f9857

NAK, this change is wrong, see how it looks in newer meta-oe: https://git.openembedded.org/meta-openembedded/commit/?id=f6df0263f768108db5c5b8c098ef0d4c699841a4

NAK meta-oe cannot depend on meta-python, fix your ostree change to respect both PTEST_ENABLED and BBFILES_COLLECTIONS. And more importantly make sure that all these changes you're proposing for dunfe

Then I believe layer index should be fixed to support longer values, there are layers which are compatible with multiple releases and it works fine with bitbake/oe-core, layer index parsing shouldn't

I think it's bad practice to claim honister support this early in its development cycle. It won't happen with well-maintained layers like meta-oe, but if some less frequently updated layer sets the co

Understood, you still do a great job catching (and fixing) most issues. Maintaining meta-oe for many years, before Armin and then you finally removed that burden from me has taught me how much work it

* after the migration to gtk3 in: https://git.openembedded.org/meta-openembedded/commit/?id=8221db74e300619d002e2b385d12a5fe13e8999a this was now failing with: | In file included from ../../gtkwave-gt

* after the migration to gtk3 in: https://git.openembedded.org/meta-openembedded/commit/?id=8221db74e300619d002e2b385d12a5fe13e8999a this was now failing with: | In file included from ../../gtkwave-gt

v2 coming soon as it actually needs both wayland and x11 (instead of either one used before), because tk requires x11 ERROR: Nothing PROVIDES 'tk' (but meta-openembedded/meta-oe/recipes-graphics/gtkwa

* after the migration to gtk3 in: https://git.openembedded.org/meta-openembedded/commit/?id=8221db74e300619d002e2b385d12a5fe13e8999a this was now failing with: | In file included from ../../gtkwave-gt