similarity index 91%
rename from meta-python/recipes-devtools/python/python3-filelock_3.32.4.bb
rename to meta-python/recipes-devtools/python/python3-filelock_4.0.4.bb
@@ -9,7 +9,7 @@ CVE_PRODUCT = "tox-dev:filelock"
SRC_URI += "file://run-ptest"
-SRC_URI[sha256sum] = "2bde2e4cf732e0153406d8a7bc80620ecf5e621fe0d25e41143c4e3b4733ff30"
+SRC_URI[sha256sum] = "90999ed63a26ccf86b93b959ab10cf1017f422d816be454ed54cbed263e71ab5"
BBCLASSEXTEND = "native nativesdk"
@@ -21,6 +21,7 @@ DEPENDS += "\
RDEPENDS:${PN} += " \
python3-core \
+ python3-crypt \
python3-logging \
python3-asyncio \
"
Add python3-crypt to RDEPENDS: the library now imports hashlib (_identity.py, pulled in by "import filelock" through the soft and strict locks). Changelog: https://github.com/tox-dev/filelock/blob/4.0.4/docs/changelog.rst 4.0.4 - Hostnames differing only past their first 253 escaped characters now publish distinct soft-lock owners. 4.0.3 - Skip the fork-safety audit hook on CPython 3.10/3.11, where it broke thread creation under coverage or a debugger. 4.0.2 - Fix OS lock leaks, double closes and false deadlocks from concurrent acquire()/release() on thread_local=False locks. - Async read-write locks give each asyncio task its own hold. 4.0.1 - Validate poll_interval at construction, on the setter and on acquire(). 4.0.0 (breaking) - SoftReadWriteLock uses a new on-disk generation-log protocol under <path>.rw that earlier releases do not see; all participants on a lock path must be upgraded together. It now requires os.link. - SoftReadWriteLock exposes a generation fencing token, reports lost holds through on_compromise, and no longer deadlocks when a holder on another host dies mid-transition. AI-Generated: Uses Claude Code Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com> --- .../{python3-filelock_3.32.4.bb => python3-filelock_4.0.4.bb} | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) rename meta-python/recipes-devtools/python/{python3-filelock_3.32.4.bb => python3-filelock_4.0.4.bb} (91%)