[oe] Yocto Project Newcomer & Unassigned Bugs - Help Needed

2024-04-15 Thread Stephen Jolley
All,

The triage team is starting to try and collect up and classify bugs which a
newcomer to the project would be able to work on in a way which means
people can find them. They're being listed on the triage page under the
appropriate heading:
https://wiki.yoctoproject.org/wiki/Bug_Triage#Newcomer_Bugs Also please
review:
https://www.openembedded.org/wiki/How_to_submit_a_patch_to_OpenEmbedded and
how to create a bugzilla account at:
https://bugzilla.yoctoproject.org/createaccount.cgi

The idea is these bugs should be straight forward for a person to help work
on who doesn't have deep experience with the project. If anyone can help,
please take ownership of the bug and send patches! If anyone needs
help/advice there are people on irc who can likely do so, or some of the
more experienced contributors will likely be happy to help too.

Also, the triage team meets weekly and does its best to handle the bugs
reported into the Bugzilla. The number of people attending that meeting has
fallen, as have the number of people available to help fix bugs. One of the
things we hear users report is they don't know how to help. We (the triage
team) are therefore going to start reporting out the currently 413
unassigned or newcomer bugs.

We're hoping people may be able to spare some time now and again to help
out with these. Bugs are split into two types, "true bugs" where things
don't work as they should and "enhancements" which are features we'd want
to add to the system. There are also roughly four different "priority"
classes right now, “5.0”, “5.1”, "5.99" and "Future", the more
pressing/urgent issues being in "5.0" and then “5.1”.

Please review this link and if a bug is something you would be able to help
with either take ownership of the bug, or send me (sjolley.yp...@gmail.com)
an e-mail with the bug number you would like and I will assign it to you
(please make sure you have a Bugzilla account). The list is at:
https://wiki.yoctoproject.org/wiki/Bug_Triage_Archive#Unassigned_or_Newcomer_Bugs

Thanks,



*Stephen K. Jolley*

*Yocto Project Program Manager*

(*Cell*:(208) 244-4460

* *Email*: *s
jolley.yp...@gmail.com *

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#109971): 
https://lists.openembedded.org/g/openembedded-devel/message/109971
Mute This Topic: https://lists.openembedded.org/mt/105545716/21656
Group Owner: openembedded-devel+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-devel/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



[oe] [meta-python][PATCH 3/3] python3-sqlalchemy: upgrade 2.0.27 -> 2.0.29

2024-04-15 Thread Tom Geelen
---
 ...ython3-sqlalchemy_2.0.27.bb => python3-sqlalchemy_2.0.29.bb} | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
 rename meta-python/recipes-devtools/python/{python3-sqlalchemy_2.0.27.bb => 
python3-sqlalchemy_2.0.29.bb} (87%)

diff --git a/meta-python/recipes-devtools/python/python3-sqlalchemy_2.0.27.bb 
b/meta-python/recipes-devtools/python/python3-sqlalchemy_2.0.29.bb
similarity index 87%
rename from meta-python/recipes-devtools/python/python3-sqlalchemy_2.0.27.bb
rename to meta-python/recipes-devtools/python/python3-sqlalchemy_2.0.29.bb
index e5a837659..e646bd0d9 100644
--- a/meta-python/recipes-devtools/python/python3-sqlalchemy_2.0.27.bb
+++ b/meta-python/recipes-devtools/python/python3-sqlalchemy_2.0.29.bb
@@ -4,7 +4,7 @@ HOMEPAGE = "http://www.sqlalchemy.org/";
 LICENSE = "MIT"
 LIC_FILES_CHKSUM = "file://LICENSE;md5=c78b979ae6c20775a28a287d32092cbb"
 
-SRC_URI[sha256sum] = 
"86a6ed69a71fe6b88bf9331594fa390a2adda4a49b5c06f98e47bf0d392534f8"
+SRC_URI[sha256sum] = 
"bd9566b8e58cabd700bc367b60e90d9349cd16f0984973f98a9a09f9c64e86f0"
 
 PYPI_PACKAGE = "SQLAlchemy"
 inherit pypi setuptools3
-- 
2.34.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#109970): 
https://lists.openembedded.org/g/openembedded-devel/message/109970
Mute This Topic: https://lists.openembedded.org/mt/105544356/21656
Group Owner: openembedded-devel+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-devel/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



[oe] [meta-python][PATCH 2/3] python3-zeroconf: upgrade 0.131.0 -> 0.132.0

2024-04-15 Thread Tom Geelen
Python3-zeroconf specifies a pyproject.toml and uses poetry as a build tool. 
Adjusted recipe accordingly
---
 ...3-zeroconf_0.131.0.bb => python3-zeroconf_0.132.0.bb} | 9 +
 1 file changed, 5 insertions(+), 4 deletions(-)
 rename meta-python/recipes-devtools/python/{python3-zeroconf_0.131.0.bb => 
python3-zeroconf_0.132.0.bb} (63%)

diff --git a/meta-python/recipes-devtools/python/python3-zeroconf_0.131.0.bb 
b/meta-python/recipes-devtools/python/python3-zeroconf_0.132.0.bb
similarity index 63%
rename from meta-python/recipes-devtools/python/python3-zeroconf_0.131.0.bb
rename to meta-python/recipes-devtools/python/python3-zeroconf_0.132.0.bb
index 4c7bebe76..ea8ef1cb9 100644
--- a/meta-python/recipes-devtools/python/python3-zeroconf_0.131.0.bb
+++ b/meta-python/recipes-devtools/python/python3-zeroconf_0.132.0.bb
@@ -3,12 +3,13 @@ HOMEPAGE = "https://github.com/jstasiak/python-zeroconf";
 LICENSE = "LGPL-2.1-only"
 LIC_FILES_CHKSUM = 
"file://PKG-INFO;beginline=6;endline=6;md5=6517bdc8f2416f27ab725d4702f7aac3"
 
-SRC_URI[sha256sum] = 
"90c431e99192a044a5e0217afd7ca0ca9824af93190332e6f7baf4da5375f331"
+SRC_URI[sha256sum] = 
"e2dddb9b8e6a9de3c43f943d8547300e6bd49b2043fd719ae830cfe0f2908a5c"
 
-inherit pypi setuptools3
+DEPENDS += "python3-cython-native"
+
+inherit pypi python_poetry_core
 
 RDEPENDS:${PN} += " \
-python3-ifaddr \
-python3-asyncio \
+python3-ifaddr (>=0.1.7) \
 python3-async-timeout \
 "
-- 
2.34.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#109969): 
https://lists.openembedded.org/g/openembedded-devel/message/109969
Mute This Topic: https://lists.openembedded.org/mt/105544354/21656
Group Owner: openembedded-devel+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-devel/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



[oe] [meta-python][PATCH 1/3] python3-pychromecast: upgrade 14.0.0 -> 14.0.1

2024-04-15 Thread Tom Geelen
---
 .../0001-Allow-newer-version-of-wheel-and-setuptools.patch| 4 ++--
 ...-pychromecast_14.0.0.bb => python3-pychromecast_14.0.1.bb} | 2 +-
 2 files changed, 3 insertions(+), 3 deletions(-)
 rename meta-python/recipes-devtools/python/{python3-pychromecast_14.0.0.bb => 
python3-pychromecast_14.0.1.bb} (84%)

diff --git 
a/meta-python/recipes-devtools/python/python3-pychromecast/0001-Allow-newer-version-of-wheel-and-setuptools.patch
 
b/meta-python/recipes-devtools/python/python3-pychromecast/0001-Allow-newer-version-of-wheel-and-setuptools.patch
index 8825615de..447f67907 100644
--- 
a/meta-python/recipes-devtools/python/python3-pychromecast/0001-Allow-newer-version-of-wheel-and-setuptools.patch
+++ 
b/meta-python/recipes-devtools/python/python3-pychromecast/0001-Allow-newer-version-of-wheel-and-setuptools.patch
@@ -1,4 +1,4 @@
-From e82caffe51b37c211f7f0cd60002fbc6b4e48d03 Mon Sep 17 00:00:00 2001
+From 5ee73f91b7f13dd5c700c69e7fc43cecab5868da Mon Sep 17 00:00:00 2001
 From: Tom Geelen 
 Date: Sun, 7 Apr 2024 22:39:35 +
 Subject: [PATCH] Allow newer version of wheel and setuptools
@@ -10,7 +10,7 @@ Signed-off-by: Tom Geelen 
  1 file changed, 1 insertion(+), 1 deletion(-)
 
 diff --git a/pyproject.toml b/pyproject.toml
-index 0f19c71..d0ecf11 100644
+index 56df5bd..17ca62d 100644
 --- a/pyproject.toml
 +++ b/pyproject.toml
 @@ -1,5 +1,5 @@
diff --git a/meta-python/recipes-devtools/python/python3-pychromecast_14.0.0.bb 
b/meta-python/recipes-devtools/python/python3-pychromecast_14.0.1.bb
similarity index 84%
rename from meta-python/recipes-devtools/python/python3-pychromecast_14.0.0.bb
rename to meta-python/recipes-devtools/python/python3-pychromecast_14.0.1.bb
index be5a3a97e..dee4bf6eb 100644
--- a/meta-python/recipes-devtools/python/python3-pychromecast_14.0.0.bb
+++ b/meta-python/recipes-devtools/python/python3-pychromecast_14.0.1.bb
@@ -4,7 +4,7 @@ LICENSE = "MIT"
 LIC_FILES_CHKSUM = "file://LICENSE;md5=b1dbd4e85f47b389bdadee9c694669f5"
 
 SRC_URI += "file://0001-Allow-newer-version-of-wheel-and-setuptools.patch"
-SRC_URI[sha256sum] = 
"dc4f8b052e760a978da9b2568b79020cb79af608a026465f07544cffe43973cf"
+SRC_URI[sha256sum] = 
"e16e0a7f9488319191b8b4fa21ca0beb4bf12eeda5c9bf640241188f2bea0a3e"
 
 PYPI_PACKAGE = "PyChromecast"
 
-- 
2.34.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#109968): 
https://lists.openembedded.org/g/openembedded-devel/message/109968
Mute This Topic: https://lists.openembedded.org/mt/105544303/21656
Group Owner: openembedded-devel+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-devel/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [oe] [meta-python2][PATCH] layer.conf: update LAYERSERIES_COMPAT for scarthgap

2024-04-15 Thread Martin Jansa
If you need it just for some experiments than feel free to use:
https://github.com/shr-project/meta-python2/commits/jansa/master/
which I've already updated (for built time benchmark which
historically included qtwebengine as well
https://github.com/shr-project/test-oe-build-time).

But for anything more serious work with your customer to switch to
something more supported, there are still minor upgrades to meta-qt5
(last in https://github.com/meta-qt5/meta-qt5/pull/556), but it's a
dead end and switch to something else should have higher priority than
switch to scarthgap (e.g. switching to meta-qt6).

Cheers,

On Mon, Apr 15, 2024 at 3:15 PM Marek Vasut  wrote:
>
> Support both kirkstone and scarthgap as that seems to work well.
>
> Signed-off-by: Marek Vasut 
> ---
>  conf/layer.conf | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/conf/layer.conf b/conf/layer.conf
> index 38ef579..0f228ca 100644
> --- a/conf/layer.conf
> +++ b/conf/layer.conf
> @@ -14,7 +14,7 @@ LAYERVERSION_meta-python2 = "1"
>
>  LAYERDEPENDS_meta-python2 = "core openembedded-layer"
>
> -LAYERSERIES_COMPAT_meta-python2 = "kirkstone"
> +LAYERSERIES_COMPAT_meta-python2 = "kirkstone scarthgap"
>
>  LICENSE_PATH += "${LAYERDIR}/licenses"
>
> --
> 2.43.0
>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#109966): 
https://lists.openembedded.org/g/openembedded-devel/message/109966
Mute This Topic: https://lists.openembedded.org/mt/105535514/21656
Group Owner: openembedded-devel+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-devel/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [oe] [meta-python2][PATCH] layer.conf: update LAYERSERIES_COMPAT for scarthgap

2024-04-15 Thread Alexander Kanavin
Yes to Tim's hard no. Qt5 itself is EOL for almost a year now (don't
tell me about their commercial offers, ok?).

I would put something similar to meta-gpl2 into that layer instead actually:
https://git.yoctoproject.org/meta-gplv2/commit/?id=43bf0e8d5985945d19d01f94bfbbda420c4435f3

Alex


On Mon, 15 Apr 2024 at 17:21, Tim Orling via lists.openembedded.org
 wrote:
>
> This is a hard no from me.
>
> On Mon, Apr 15, 2024 at 6:59 AM Marek Vasut via lists.openembedded.org 
>  wrote:
>>
>> On 4/15/24 3:49 PM, Jose Quaresma wrote:
>> > Hi Marek,
>>
>> Hi,
>>
>> > Last commit on this layer was done 2 years ago and it was at the time to
>> > add Kirkstone compatibility, nothing more since then.
>> > Python 2 is dead since 1/1/2020. That means that we (python dev) will not
>> > improve it anymore after that day,
>> > even if someone finds a security problem in it. You should upgrade to
>> > Python 3 as soon as you can.
>> >
>> > https://www.python.org/doc/sunset-python-2
>> >
>> > In my opinion the OE community should no longer promote its use.
>>
>> I am aware of this, for me this is just a band-aid to keep meta-qt5
>> building for a while longer. I can work around this in bblayers.conf or
>> local.conf too, I would like to avoid that however.
>>
>>
>>
>
> 
>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#109965): 
https://lists.openembedded.org/g/openembedded-devel/message/109965
Mute This Topic: https://lists.openembedded.org/mt/105535514/21656
Group Owner: openembedded-devel+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-devel/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [oe] [meta-python2][PATCH] layer.conf: update LAYERSERIES_COMPAT for scarthgap

2024-04-15 Thread Tim Orling
This is a hard no from me.

On Mon, Apr 15, 2024 at 6:59 AM Marek Vasut via lists.openembedded.org
 wrote:

> On 4/15/24 3:49 PM, Jose Quaresma wrote:
> > Hi Marek,
>
> Hi,
>
> > Last commit on this layer was done 2 years ago and it was at the time to
> > add Kirkstone compatibility, nothing more since then.
> > Python 2 is dead since 1/1/2020. That means that we (python dev) will not
> > improve it anymore after that day,
> > even if someone finds a security problem in it. You should upgrade to
> > Python 3 as soon as you can.
> >
> > https://www.python.org/doc/sunset-python-2
> >
> > In my opinion the OE community should no longer promote its use.
>
> I am aware of this, for me this is just a band-aid to keep meta-qt5
> building for a while longer. I can work around this in bblayers.conf or
> local.conf too, I would like to avoid that however.
>
> 
>
>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#109964): 
https://lists.openembedded.org/g/openembedded-devel/message/109964
Mute This Topic: https://lists.openembedded.org/mt/105535514/21656
Group Owner: openembedded-devel+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-devel/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [oe] [meta-python2][PATCH] layer.conf: update LAYERSERIES_COMPAT for scarthgap

2024-04-15 Thread Marek Vasut

On 4/15/24 3:49 PM, Jose Quaresma wrote:

Hi Marek,


Hi,


Last commit on this layer was done 2 years ago and it was at the time to
add Kirkstone compatibility, nothing more since then.
Python 2 is dead since 1/1/2020. That means that we (python dev) will not
improve it anymore after that day,
even if someone finds a security problem in it. You should upgrade to
Python 3 as soon as you can.

https://www.python.org/doc/sunset-python-2

In my opinion the OE community should no longer promote its use.


I am aware of this, for me this is just a band-aid to keep meta-qt5 
building for a while longer. I can work around this in bblayers.conf or 
local.conf too, I would like to avoid that however.

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#109963): 
https://lists.openembedded.org/g/openembedded-devel/message/109963
Mute This Topic: https://lists.openembedded.org/mt/105535514/21656
Group Owner: openembedded-devel+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-devel/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [oe] [meta-python2][PATCH] layer.conf: update LAYERSERIES_COMPAT for scarthgap

2024-04-15 Thread Jose Quaresma
Hi Marek,

Last commit on this layer was done 2 years ago and it was at the time to
add Kirkstone compatibility, nothing more since then.
Python 2 is dead since 1/1/2020. That means that we (python dev) will not
improve it anymore after that day,
even if someone finds a security problem in it. You should upgrade to
Python 3 as soon as you can.

https://www.python.org/doc/sunset-python-2

In my opinion the OE community should no longer promote its use.

Jose

Marek Vasut via lists.openembedded.org 
escreveu (segunda, 15/04/2024 à(s) 14:15):

> Support both kirkstone and scarthgap as that seems to work well.
>
> Signed-off-by: Marek Vasut 
> ---
>  conf/layer.conf | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/conf/layer.conf b/conf/layer.conf
> index 38ef579..0f228ca 100644
> --- a/conf/layer.conf
> +++ b/conf/layer.conf
> @@ -14,7 +14,7 @@ LAYERVERSION_meta-python2 = "1"
>
>  LAYERDEPENDS_meta-python2 = "core openembedded-layer"
>
> -LAYERSERIES_COMPAT_meta-python2 = "kirkstone"
> +LAYERSERIES_COMPAT_meta-python2 = "kirkstone scarthgap"
>
>  LICENSE_PATH += "${LAYERDIR}/licenses"
>
> --
> 2.43.0
>
>
> 
>
>

-- 
Best regards,

José Quaresma

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#109962): 
https://lists.openembedded.org/g/openembedded-devel/message/109962
Mute This Topic: https://lists.openembedded.org/mt/105535514/21656
Group Owner: openembedded-devel+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-devel/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



[oe] [meta-python2][PATCH] layer.conf: update LAYERSERIES_COMPAT for scarthgap

2024-04-15 Thread Marek Vasut
Support both kirkstone and scarthgap as that seems to work well.

Signed-off-by: Marek Vasut 
---
 conf/layer.conf | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/conf/layer.conf b/conf/layer.conf
index 38ef579..0f228ca 100644
--- a/conf/layer.conf
+++ b/conf/layer.conf
@@ -14,7 +14,7 @@ LAYERVERSION_meta-python2 = "1"
 
 LAYERDEPENDS_meta-python2 = "core openembedded-layer"
 
-LAYERSERIES_COMPAT_meta-python2 = "kirkstone"
+LAYERSERIES_COMPAT_meta-python2 = "kirkstone scarthgap"
 
 LICENSE_PATH += "${LAYERDIR}/licenses"
 
-- 
2.43.0


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#109961): 
https://lists.openembedded.org/g/openembedded-devel/message/109961
Mute This Topic: https://lists.openembedded.org/mt/105535514/21656
Group Owner: openembedded-devel+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-devel/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [oe] [meta-oe][PATCH] edid-decode: allow to build native variant

2024-04-15 Thread Markus Volk
Thats absolutely true . But still I dont think it is a bug in the 
libdisplay-info build system, because edid-decode is requested for the 
tests and is requested native explicitly.


On Mon, Apr 15 2024 at 11:41:38 AM +00:00:00, Ross Burton 
 wrote:



 On 15 Apr 2024, at 12:32, Markus Volk > wrote:


 On Mon, Apr 15 2024 at 11:07:45 AM +00:00:00, Ross Burton 
mailto:ross.bur...@arm.com>> wrote:
 Surely that´s a bug in the meson.build? It doesn´t want to find 
a native binary.



 Its added here, I think mostly for testing purpose:

 

 

 

 



 If edid-decode is added a s a native dependency, an additional 
binary will be installed '/usr/bin/di-edid-decode’


Are you sure about that?  All of those references are specific to the 
test suite (which would want native binaries, unless they make the 
effort to support installable tests).  The di-edid-decode binary is 
buillt and installed by 
 
which doesn’t have any conditionals.


Ross



-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#109960): 
https://lists.openembedded.org/g/openembedded-devel/message/109960
Mute This Topic: https://lists.openembedded.org/mt/105516163/21656
Group Owner: openembedded-devel+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-devel/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [oe] [meta-oe][PATCH] edid-decode: allow to build native variant

2024-04-15 Thread Ross Burton


> On 15 Apr 2024, at 12:32, Markus Volk  wrote:
> 
> On Mon, Apr 15 2024 at 11:07:45 AM +00:00:00, Ross Burton 
>  wrote:
>> Surely that´s a bug in the meson.build? It doesn´t want to find a native 
>> binary.
> 
> 
> Its added here, I think mostly for testing purpose:
> 
> https://gitlab.freedesktop.org/emersion/libdisplay-info/-/blob/main/test/meson.build#L1
> https://gitlab.freedesktop.org/emersion/libdisplay-info/-/blob/main/test/meson.build#L10
> https://gitlab.freedesktop.org/emersion/libdisplay-info/-/blob/main/test/meson.build#L59
> https://gitlab.freedesktop.org/emersion/libdisplay-info/-/blob/main/test/meson.build#L66
> 
> If edid-decode is added a s a native dependency, an additional binary will be 
> installed '/usr/bin/di-edid-decode’

Are you sure about that?  All of those references are specific to the test 
suite (which would want native binaries, unless they make the effort to support 
installable tests).  The di-edid-decode binary is buillt and installed by 
https://gitlab.freedesktop.org/emersion/libdisplay-info/-/blob/main/di-edid-decode/meson.build
 which doesn’t have any conditionals.

Ross
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#109959): 
https://lists.openembedded.org/g/openembedded-devel/message/109959
Mute This Topic: https://lists.openembedded.org/mt/105516163/21656
Group Owner: openembedded-devel+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-devel/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [oe] [meta-oe][PATCH] edid-decode: allow to build native variant

2024-04-15 Thread Markus Volk
On Mon, Apr 15 2024 at 11:07:45 AM +00:00:00, Ross Burton 
 wrote:
Surely that’s a bug in the meson.build?  It doesn’t want to find 
a native binary.


Its added here, I think mostly for testing purpose:






If edid-decode is added a s a native dependency, an additional binary 
will be installed '/usr/bin/di-edid-decode'



-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#109958): 
https://lists.openembedded.org/g/openembedded-devel/message/109958
Mute This Topic: https://lists.openembedded.org/mt/105516163/21656
Group Owner: openembedded-devel+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-devel/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



[oe] [meta-oe][PATCH 2/2] docopt.cpp: add support for native and nativesdk

2024-04-15 Thread Eero Aaltonen via lists.openembedded.org
From: Eero Aaltonen 

There are use cases for build time cli tools, so include support for
native as well.

Signed-off-by: Eero Aaltonen 
---
 meta-oe/recipes-extended/docopt.cpp/docopt.cpp_git.bb | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/meta-oe/recipes-extended/docopt.cpp/docopt.cpp_git.bb 
b/meta-oe/recipes-extended/docopt.cpp/docopt.cpp_git.bb
index 87eed4b656..ec0b4da935 100644
--- a/meta-oe/recipes-extended/docopt.cpp/docopt.cpp_git.bb
+++ b/meta-oe/recipes-extended/docopt.cpp/docopt.cpp_git.bb
@@ -26,3 +26,5 @@ inherit cmake
 
 PACKAGECONFIG ??= ""
 PACKAGECONFIG[boost] = "-DUSE_BOOST_REGEX=ON,-DUSE_BOOST_REGEX=OFF,boost"
+
+BBCLASSEXTEND = "native nativesdk"
-- 
2.34.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#109957): 
https://lists.openembedded.org/g/openembedded-devel/message/109957
Mute This Topic: https://lists.openembedded.org/mt/105533651/21656
Group Owner: openembedded-devel+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-devel/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



[oe] [meta-oe][PATCH 1/2] docopt.cpp: turn boost to a PACKAGECONFIG option

2024-04-15 Thread Eero Aaltonen via lists.openembedded.org
From: Eero Aaltonen 

docopt.cpp only uses boost regex with the option USE_BOOST_REGEX=ON.
When used, boost regex is statically linked.

Signed-off-by: Eero Aaltonen 
---
 meta-oe/recipes-extended/docopt.cpp/docopt.cpp_git.bb | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/meta-oe/recipes-extended/docopt.cpp/docopt.cpp_git.bb 
b/meta-oe/recipes-extended/docopt.cpp/docopt.cpp_git.bb
index 3d438871ed..87eed4b656 100644
--- a/meta-oe/recipes-extended/docopt.cpp/docopt.cpp_git.bb
+++ b/meta-oe/recipes-extended/docopt.cpp/docopt.cpp_git.bb
@@ -13,7 +13,6 @@ LIC_FILES_CHKSUM = "\
 file://LICENSE-MIT;md5=4b242fd9ef20207e18286d73da8a6677 \
 "
 
-DEPENDS = "boost"
 SRCREV = "42ebcec9dc2c99a1b3a4542787572045763ad196"
 PV = "0.6.3+git"
 
@@ -24,3 +23,6 @@ SRC_URI = "\
 S = "${WORKDIR}/git"
 
 inherit cmake
+
+PACKAGECONFIG ??= ""
+PACKAGECONFIG[boost] = "-DUSE_BOOST_REGEX=ON,-DUSE_BOOST_REGEX=OFF,boost"
-- 
2.34.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#109956): 
https://lists.openembedded.org/g/openembedded-devel/message/109956
Mute This Topic: https://lists.openembedded.org/mt/105533646/21656
Group Owner: openembedded-devel+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-devel/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [oe] [meta-oe][PATCH] edid-decode: allow to build native variant

2024-04-15 Thread Ross Burton
On 14 Apr 2024, at 13:58, Markus Volk via lists.openembedded.org 
 wrote:
> 
> This is a requirement for libdisplay-info and fixes:
> Program edid-decode found: NO

Surely that’s a bug in the meson.build?  It doesn’t want to find a native 
binary.

Ross
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#109955): 
https://lists.openembedded.org/g/openembedded-devel/message/109955
Mute This Topic: https://lists.openembedded.org/mt/105516163/21656
Group Owner: openembedded-devel+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-devel/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [oe] [meta-oe][PATCH] c-ares: Improve the ptest output

2024-04-15 Thread Peter Marko via lists.openembedded.org
-Original Message-
From: openembedded-devel@lists.openembedded.org 
 On Behalf Of Yu, Mingli via 
lists.openembedded.org
Sent: Monday, April 15, 2024 11:08
To: openembedded-devel@lists.openembedded.org
Subject: [oe] [meta-oe][PATCH] c-ares: Improve the ptest output

> From: Mingli Yu 
>
> Before the patch:
>  # ./run-ptest
> [snip]
> [ DISABLED ] LibraryTest.DISABLED_ParseAReplyVariantCnameLast
> [ RUN  ] LibraryTest.ParseAReplyErrors
> [   OK ] LibraryTest.ParseAReplyErrors (4 ms)
> [ RUN  ] LibraryTest.ParseAReplyAllocFail
> [   OK ] LibraryTest.ParseAReplyAllocFail (0 ms)
> [snip]
>
> After the patch:
>  # ./run-ptest
> [snip]
> SKIP:  LibraryTest.DISABLED_ParseAReplyVariantCnameLast
> PASS:  LibraryTest.ParseAReplyErrors
> PASS:  LibraryTest.ParseAReplyAllocFail
> [snip]
>
> Signed-off-by: Mingli Yu 
> ---
>  meta-oe/recipes-support/c-ares/c-ares/run-ptest | 6 +-
>  1 file changed, 1 insertion(+), 5 deletions(-)
>
> diff --git a/meta-oe/recipes-support/c-ares/c-ares/run-ptest 
> b/meta-oe/recipes-support/c-ares/c-ares/run-ptest
> index 46572111b..66ffd5388 100644
> --- a/meta-oe/recipes-support/c-ares/c-ares/run-ptest
> +++ b/meta-oe/recipes-support/c-ares/c-ares/run-ptest
> @@ -1,7 +1,3 @@
>  #!/bin/sh
> +./arestest --gtest_filter=-*.Live* --gtest_print_time=0 | sed -E  '/^\[ 
> RUN/d ; s/\[   OK \]/PASS: / ; s/\[ DISABLED \]/SKIP: / ; s/\[ FAILED 
> \]/FAIL: /'

There is a general problem with piping the test output that the result code of 
the test is ignored (result code of sed is used).
I tend to use "(test || echo 'FAIL: exit code') | sed ...", but that usually 
adds another failed testcase printed in addition to the real failed testcase.
However I have seen that test binary can fail without printing test failure 
(e.g. wrong path, missing executable rights, segmentation fault, ...) so exit 
code is important to be checked.

I'd appreciate if yocto elders would give some hints about how the run-ptest 
should be written if it does not support automake output format.
I'm rewriting lot of gtest based ptests right now when preparing upgrade from 
kirkstone to scarthgap due to test output format enforcement and this is giving 
me headaches...

>  
> -if ./arestest --gtest_filter=-*.Live*; then
> - echo "PASS: c-ares"
> -else
> - echo "FAIL: c-ares"
> -fi
> -- 
> 2.25.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#109954): 
https://lists.openembedded.org/g/openembedded-devel/message/109954
Mute This Topic: https://lists.openembedded.org/mt/105532398/21656
Group Owner: openembedded-devel+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-devel/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



[oe] [meta-oe][PATCH] c-ares: Improve the ptest output

2024-04-15 Thread Yu, Mingli
From: Mingli Yu 

Before the patch:
 # ./run-ptest
[snip]
[ DISABLED ] LibraryTest.DISABLED_ParseAReplyVariantCnameLast
[ RUN  ] LibraryTest.ParseAReplyErrors
[   OK ] LibraryTest.ParseAReplyErrors (4 ms)
[ RUN  ] LibraryTest.ParseAReplyAllocFail
[   OK ] LibraryTest.ParseAReplyAllocFail (0 ms)
[snip]

After the patch:
 # ./run-ptest
[snip]
SKIP:  LibraryTest.DISABLED_ParseAReplyVariantCnameLast
PASS:  LibraryTest.ParseAReplyErrors
PASS:  LibraryTest.ParseAReplyAllocFail
[snip]

Signed-off-by: Mingli Yu 
---
 meta-oe/recipes-support/c-ares/c-ares/run-ptest | 6 +-
 1 file changed, 1 insertion(+), 5 deletions(-)

diff --git a/meta-oe/recipes-support/c-ares/c-ares/run-ptest 
b/meta-oe/recipes-support/c-ares/c-ares/run-ptest
index 46572111b..66ffd5388 100644
--- a/meta-oe/recipes-support/c-ares/c-ares/run-ptest
+++ b/meta-oe/recipes-support/c-ares/c-ares/run-ptest
@@ -1,7 +1,3 @@
 #!/bin/sh
+./arestest --gtest_filter=-*.Live* --gtest_print_time=0 | sed -E  '/^\[ RUN/d 
; s/\[   OK \]/PASS: / ; s/\[ DISABLED \]/SKIP: / ; s/\[ FAILED \]/FAIL: /'
 
-if ./arestest --gtest_filter=-*.Live*; then
-   echo "PASS: c-ares"
-else
-   echo "FAIL: c-ares"
-fi
-- 
2.25.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#109953): 
https://lists.openembedded.org/g/openembedded-devel/message/109953
Mute This Topic: https://lists.openembedded.org/mt/105532398/21656
Group Owner: openembedded-devel+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-devel/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-