|
[AUH] python3-cffi: upgrading to 1.15.1 SUCCEEDED
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *python3-cffi* to *1.15.1* has Succeeded.
Next steps:
- apply the patch: git am
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *python3-cffi* to *1.15.1* has Succeeded.
Next steps:
- apply the patch: git am
|
By
Auto Upgrade Helper
·
#167485
·
|
|
[AUH] python3-jsonschema: upgrading to 4.6.1 SUCCEEDED
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *python3-jsonschema* to *4.6.1* has Succeeded.
Next steps:
- apply the patch:
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *python3-jsonschema* to *4.6.1* has Succeeded.
Next steps:
- apply the patch:
|
By
Auto Upgrade Helper
·
#167484
·
|
|
[AUH] llvm: upgrading to 14.0.6 FAILED
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *llvm* to *14.0.6* has Failed (devtool error).
Detailed error information:
The
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *llvm* to *14.0.6* has Failed (devtool error).
Detailed error information:
The
|
By
Auto Upgrade Helper
·
#167483
·
|
|
[AUH] glib-networking: upgrading to 2.72.1 SUCCEEDED
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *glib-networking* to *2.72.1* has Succeeded.
Next steps:
- apply the patch: git
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *glib-networking* to *2.72.1* has Succeeded.
Next steps:
- apply the patch: git
|
By
Auto Upgrade Helper
·
#167482
·
|
|
[AUH] git: upgrading to 2.37.0 SUCCEEDED
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *git* to *2.37.0* has Succeeded.
Next steps:
- apply the patch: git am
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *git* to *2.37.0* has Succeeded.
Next steps:
- apply the patch: git am
|
By
Auto Upgrade Helper
·
#167481
·
|
|
[AUH] dmidecode: upgrading to 3.4 SUCCEEDED
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *dmidecode* to *3.4* has Succeeded.
Next steps:
- apply the patch: git am
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *dmidecode* to *3.4* has Succeeded.
Next steps:
- apply the patch: git am
|
By
Auto Upgrade Helper
·
#167480
·
|
|
[AUH] cargo: upgrading to 1.62.0 FAILED
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *cargo* to *1.62.0* has Failed(other errors).
Detailed error
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *cargo* to *1.62.0* has Failed(other errors).
Detailed error
|
By
Auto Upgrade Helper
·
#167479
·
|
|
[AUH] glib-2.0: upgrading to 2.72.3 SUCCEEDED
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *glib-2.0* to *2.72.3* has Succeeded.
Next steps:
- apply the patch: git am
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *glib-2.0* to *2.72.3* has Succeeded.
Next steps:
- apply the patch: git am
|
By
Auto Upgrade Helper
·
#167478
·
|
|
[AUH] openssl: upgrading to 3.0.4 FAILED
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *openssl* to *3.0.4* has Failed (devtool error).
Detailed error
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *openssl* to *3.0.4* has Failed (devtool error).
Detailed error
|
By
Auto Upgrade Helper
·
#167477
·
|
|
Re: [PATCH 0/7] kernel-yocto: consolidated pull request
lists.openembedded.org wrote:
This breaks:
override PYTHON := $(call get-executable-or-default,PYTHON,$(subst -config,,$(PYTHON_AUTO)))
as somehow PYTHON is expanded to a full path, yet:
override
lists.openembedded.org wrote:
This breaks:
override PYTHON := $(call get-executable-or-default,PYTHON,$(subst -config,,$(PYTHON_AUTO)))
as somehow PYTHON is expanded to a full path, yet:
override
|
By
Richard Purdie
·
#167476
·
|
|
Re: [PATCH]] Update to 7.84.0
Khem Raj <raj.khem@...> escreveu no dia sexta, 1/07/2022 à(s) 14:58:
thanks, fixed in v2
--
Best regards,
José Quaresma
Khem Raj <raj.khem@...> escreveu no dia sexta, 1/07/2022 à(s) 14:58:
thanks, fixed in v2
--
Best regards,
José Quaresma
|
By
Jose Quaresma
·
#167475
·
|
|
[PATCH v2] curl: Update to 7.84.0
Signed-off-by: Jose Quaresma <jose.quaresma@...>
---
meta/recipes-support/curl/{curl_7.83.1.bb => curl_7.84.0.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename
Signed-off-by: Jose Quaresma <jose.quaresma@...>
---
meta/recipes-support/curl/{curl_7.83.1.bb => curl_7.84.0.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename
|
By
Jose Quaresma
·
#167474
·
|
|
Re: [PATCH 0/7] kernel-yocto: consolidated pull request
lists.openembedded.org wrote:
Confirmed that it is this change. Not sure why but at least we have an
idea of where the isssue is.
I've also sent a patch to insane.bbclass to change WARN_QA such that
lists.openembedded.org wrote:
Confirmed that it is this change. Not sure why but at least we have an
idea of where the isssue is.
I've also sent a patch to insane.bbclass to change WARN_QA such that
|
By
Richard Purdie
·
#167473
·
|
|
[PATCH] insane: Add buildpaths to WARN_QA by default
This was never enabled originally as there were a ton of warnings and
we weren't able to fix them. Now we have reproducibile builds, this can
be enabled by default as there shouldn't be such paths any
This was never enabled originally as there were a ton of warnings and
we weren't able to fix them. Now we have reproducibile builds, this can
be enabled by default as there shouldn't be such paths any
|
By
Richard Purdie
·
#167472
·
|
|
Re: [meta-zephyr] meets create-spdx
This appears to be the actual error: python3:do_create_spdx can't find
the recipe-gnu-config-native.spdx.json. I'm not sure why that would be
the case though; do_create_spdx for gnu-config-native
This appears to be the actual error: python3:do_create_spdx can't find
the recipe-gnu-config-native.spdx.json. I'm not sure why that would be
the case though; do_create_spdx for gnu-config-native
|
By
Joshua Watt
·
#167471
·
|
|
Re: [PATCH]] Update to 7.84.0
subject is missing recipe name.
subject is missing recipe name.
|
By
Khem Raj
·
#167470
·
|
|
[PATCH]] Update to 7.84.0
Signed-off-by: Jose Quaresma <jose.quaresma@...>
---
meta/recipes-support/curl/{curl_7.83.1.bb => curl_7.84.0.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename
Signed-off-by: Jose Quaresma <jose.quaresma@...>
---
meta/recipes-support/curl/{curl_7.83.1.bb => curl_7.84.0.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename
|
By
Jose Quaresma
·
#167469
·
|
|
Re: [PATCH v5 3/7] insane.bbclass: Make do_qa_staging check shebangs
lists.openembedded.org wrote:
Sorry about the delay on this. My concern isn't an issue as I wasn't
remembering the exact context of this code correctly. The patches have
therefore merged,
lists.openembedded.org wrote:
Sorry about the delay on this. My concern isn't an issue as I wasn't
remembering the exact context of this code correctly. The patches have
therefore merged,
|
By
Richard Purdie
·
#167468
·
|
|
Re: [PATCH 0/7] kernel-yocto: consolidated pull request
lists.openembedded.org wrote:
This looked a little suspicious to
lists.openembedded.org wrote:
This looked a little suspicious to
|
By
Richard Purdie
·
#167467
·
|
|
Re: [PATCH] package_manager/ipk: do not pipe stderr to stdout
Yes, certainly.
Alex
<shruthi.ravichandran@...> wrote:
Yes, certainly.
Alex
<shruthi.ravichandran@...> wrote:
|
By
Alexander Kanavin
·
#167466
·
|