python3-scons: upgrade to v4.5.2
PATCH 1/1 python3-scons: upgrade to v4.5.2
* fixes:
https://github.com/SCons/scons/issues/4231
which caused e.g. iotifity to fail in do_compile
---
.../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%)meta/recipes-devtools/python/python3-scons_4.5.2.bb renamed from meta/recipes-devtools/python/python3-scons_4.5.1.bb +1 -1
@@ -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"
Signature · 1 line
2.40.0
Quoted 3 lines · Martin Jansa
* fixes:
https://github.com/SCons/scons/issues/4231
which caused e.g. iotifity to fail indo_compile
I think that should be 4321!
Cheers,
Richard
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?
Cheers,
Quoted 11 lines · Richard Purdie
Quoted 3 lines · Martin Jansa
* fixes:
https://github.com/SCons/scons/issues/4231
which caused e.g. iotifity to fail indo_compileI think that should be 4321!
Cheers,
Richard
Quoted 6 lines · Martin Jansa
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
Quoted 6 lines · Richard Purdie
Quoted 5 lines · Martin Jansa
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).
Quoted 6 lines
Quoted 1 line
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