[OE-core][dunfell][PATCH v2] wireless-regdb: Upgrade 2019.06.03 -> 2020.04.29

2020-05-23 Thread Adrian Bunk
From: Adrian Bunk (From OE-Core rev: 5b71a3f3d1bca6b52f53b97971131a6771618420) Signed-off-by: Adrian Bunk Signed-off-by: Richard Purdie --- This is regulatory data containing the legal wifi frequencies for most countries. --- ...reless-regdb_2019.06.03.bb => wireless-regdb_2020.04.29.bb} | 3

[OE-core][dunfell][PATCH v2] git: Upgrade 2.24.1 -> 2.24.3

2020-05-23 Thread Adrian Bunk
This includes the fixes for CVE-2020-5260 and CVE-2020-11008. Signed-off-by: Adrian Bunk --- meta/recipes-devtools/git/git_2.24.1.bb | 11 --- meta/recipes-devtools/git/git_2.24.3.bb | 9 + 2 files changed, 9 insertions(+), 11 deletions(-) delete mode 100644 meta/recipes-devtoo

Re: [OE-core] [PATCH] docbook-xml: update recipe to stick with the upstream

2020-05-23 Thread Alexander Kanavin
Thanks, this looks fine now. Alex On Sat, 23 May 2020 at 21:12, Gregor Zatko wrote: > From: Gregor Zatko > > Until now a Debian package has been used as a source. > This change just switches it to project's upstream. > > https://bugzilla.yoctoproject.org/show_bug.cgi?id=13270 > > Signed-off-by

[OE-core] [PATCH] sanity.bbclass: Detect and fail if 'inherit' is used in conf file

2020-05-23 Thread Gregor Zatko
'inherit' directive may not be used in conf files as it's supposed to be used for the inheritance of classes. Correct form in conf file is INHERIT. This commit adds: - a sanity check to find whether the wrong case exists - fail the build if so - tell user about the difference in directives https:

Re: [OE-core] [PATCH] sanity.bbclass: Detect and fail if 'inherit' is used in conf file

2020-05-23 Thread Robert P. J. Day
On Sat, 23 May 2020, Gregor Zatko wrote: > 'inherit' directive may not be used in conf files as it's supposed > to be used for the inheritance of recipes. no, it's for the inheritance of class files. rday -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply O

[OE-core] [PATCH] sanity.bbclass: Detect and fail if 'inherit' is used in conf file

2020-05-23 Thread Gregor Zatko
'inherit' directive may not be used in conf files as it's supposed to be used for the inheritance of recipes. Correct form in conf file is INHERIT. This commit adds: - a sanity check to find whether the wrong case exists - fail the build if so - tell user about the difference in directives https:

[OE-core] ✗ patchtest: failure for Detect and fail if 'inherit' is used in conf file

2020-05-23 Thread Patchwork
== Series Details == Series: Detect and fail if 'inherit' is used in conf file Revision: 1 URL : https://patchwork.openembedded.org/series/24289/ State : failure == Summary == Thank you for submitting this patch series to OpenEmbedded Core. This is an automated response. Several tests have be

[OE-core] [PATCH] Detect and fail if 'inherit' is used in conf file

2020-05-23 Thread Gregor Zatko
'inherit' directive may not be used in conf files as it's supposed to be used for the inheritance of recipes. Correct form in conf file is INHERIT. This commit adds: - a sanity check to find whether the wrong case exists - fail the build if so - tell user about the difference in directives https:

[OE-core] [zeus/dunfell PATCH] avahi: Don't advertise example services by default

2020-05-23 Thread Paul Barker
The example service files are placed into /etc/avahi/services when we run `make install` for avahi. This results in ssh and sftp-ssh services being announced by default even if no ssh server is installed in an image. These example files should be moved away to another location such as /usr/share/d

[OE-core] [PATCH] docbook-xml: update recipe to stick with the upstream

2020-05-23 Thread Gregor Zatko
From: Gregor Zatko Until now a Debian package has been used as a source. This change just switches it to project's upstream. https://bugzilla.yoctoproject.org/show_bug.cgi?id=13270 Signed-off-by: Gregor Zatko --- .../docbook-xml-update-catalog.xml.patch | 515 -- .../docb

Re: [OE-core] [PATCH] docbook-xml: update recipe to stick with the upstream

2020-05-23 Thread Gregor Zatko
Yes I think so. I supposed that if there's only 4 catalogs it can be done this way but if the policy is to download everything then OK - I'll rewrite the recipe, hope this time finally well. G. On Sat, 2020-05-23 at 20:50 +0200, Alexander Kanavin wrote: > Can the original source be fetched though?

Re: [OE-core] [PATCH] docbook-xml: update recipe to stick with the upstream

2020-05-23 Thread Alexander Kanavin
Can the original source be fetched though? Copying things over into the layer itself is not the best option. Alex On Sat, 23 May 2020 at 19:20, Gregor Zatko wrote: > From: Gregor Zatko > > Until now a Debian package has been used as a source. > This change just switches it to project's upstrea

Re: [OE-core] [meta-oe][PATCH] 2/2] package_{ipk, deb, rpm}.bbclass: support per package user-defined metadata.

2020-05-23 Thread Paulo Neve
I was in the middle of making a test set based on Alexander suggestion but it seems i need to redo all my workspace every time i run the tests, which is terrible for iteration. Am i missing something? oe-selftest -r package.PackageTests.test_custom_metadata_is_in_package_indexcd ../poky-selftest-s

[OE-core] [PATCH] docbook-xml: update recipe to stick with the upstream

2020-05-23 Thread Gregor Zatko
From: Gregor Zatko Until now a Debian package has been used as a source. This change just switches it to project's upstream. https://bugzilla.yoctoproject.org/show_bug.cgi?id=13270 Signed-off-by: Gregor Zatko --- .../docbook-xml-dtd4/catalogs/catalog-4.2.xml | 115 .../docbook-xml-dtd4/c

Re: [OE-core] can't create boost_context lib for boost-native

2020-05-23 Thread Alexander Kanavin
The problematic bit is: # only supported by x86 and powerpc BOOST_LIBS_append_x86 = " context coroutine" BOOST_LIBS_append_x86-64 = " context coroutine" BOOST_LIBS_append_powerpc = " context coroutine" BOOST_LIBS_append_arm = " context coroutine" BOOST_LIBS_append_aarch64 = " context coroutine" #

[OE-core] can't create boost_context lib for boost-native

2020-05-23 Thread Konrad Weihmann
Hi all, For reasons that are beyond my control I need to have boost_context available from boost-native. Unfortunately I didn't found a way of enabling it by a bbappend, only a full fork of the recipe would help. It seems to be caused by that single line BOOST_LIBS_remove_class-native = " co