* fixes:
https://github.com/SCons/scons/issues/4231
which caused e.g. iotifity to fail in do_compile

Signed-off-by: Martin Jansa <Martin.Jansa@...>
---
.../python/{python3-scons_4.5.1.bb => python3-scons_4.5.2.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-devtools/python/{python3-scons_4.5.1.bb => python3-scons_4.5.2.bb} (90%)

diff --git a/meta/recipes-devtools/python/python3-scons_4.5.1.bb b/meta/recipes-devtools/python/python3-scons_4.5.2.bb
similarity index 90%
rename from meta/recipes-devtools/python/python3-scons_4.5.1.bb
rename to meta/recipes-devtools/python/python3-scons_4.5.2.bb
index 279347ac9c..e0173a309e 100644
--- a/meta/recipes-devtools/python/python3-scons_4.5.1.bb
+++ b/meta/recipes-devtools/python/python3-scons_4.5.2.bb
@@ -5,7 +5,7 @@ LICENSE = "MIT"
LIC_FILES_CHKSUM = "file://LICENSE;md5=d903b0b8027f461402bac9b5169b36f7"

SRC_URI += " file://0001-Fix-man-page-installation.patch"
-SRC_URI[sha256sum] = "9daeabe4d87ba2bd4ea15410765fc1ed2d931b723e4dc730a487a3911b9a1738"
+SRC_URI[sha256sum] = "813360b2bce476bc9cc12a0f3a22d46ce520796b352557202cb07d3e402f5458"

PYPI_PACKAGE = "SCons"

--
2.40.0

On Fri, 2023-03-24 at 15:16 +0100, Martin Jansa wrote:

* fixes:
https://github.com/SCons/scons/issues/4231
which caused e.g. iotifity to fail in do_compile

I think that should be 4321!

Cheers,

Richard

On Sun, 2023-03-26 at 10:57 +0200, Martin Jansa wrote:

You're right, the commit which fixed the issue:
https://github.com/SCons/scons/commit/a4ab466c6df5bd3187e78c36bfa8f68e1fb7659e
said #4231 so I went with this less cool number (without noticing
that my other tab has the issue ticket #4321).

Should I send v2?

Please. There is some issue breaking master-next and I worry it is
something which already made it into master as there are only a limited
set of possibilities in -next including this. I can't quite see how it
would be related to this one but it is why I was looking...

Cheers,

Richard

On Sun, 2023-03-26 at 10:00 +0100, Richard Purdie wrote:

On Sun, 2023-03-26 at 10:57 +0200, Martin Jansa wrote:

You're right, the commit which fixed the issue:
https://github.com/SCons/scons/commit/a4ab466c6df5bd3187e78c36bfa8f68e1fb7659e
said #4231 so I went with this less cool number (without noticing
that my other tab has the issue ticket #4321).

Should I send v2?

Please. There is some issue breaking master-next and I worry it is
something which already made it into master as there are only a limited
set of possibilities in -next including this. I can't quite see how it
would be related to this one but it is why I was looking...

I found the problem patch and this one otherwise tested fine so I
tweaked the message.

Cheers,

Richard