Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Yegor Yefremov <yegorslists@googlemail.com>
To: buildroot@buildroot.org
Cc: James Hilliard <james.hilliard1@gmail.com>
Subject: [Buildroot] [PATCH 2/2] package/python-zlmdb: bump to version 26.7.1
Date: Tue, 13 Oct 2026 16:04:23 +0200	[thread overview]
Message-ID: <20261013140423.1941069-2-yegorslists@googlemail.com> (raw)
In-Reply-To: <20261013140423.1941069-1-yegorslists@googlemail.com>

Version 23.1.1 ships a vendored copy of flatbuffers as a top-level
"flatbuffers" package, which conflicts with python-flatbuffers that
python-zlmdb itself selects:

  FileExistsError: File already exists: .../target/usr/lib/python3.14/site-packages/flatbuffers/__init__.py

Starting with this release the flatbuffers runtime is vendored as
zlmdb.flatbuffers, and py-lmdb plus a patched LMDB are vendored as
zlmdb._lmdb_vendor, built as a CFFI extension. Thus drop the
python-flatbuffers and python-lmdb selects.

The build system switched to hatchling. The build hook needs host cffi
and setuptools to compile the LMDB extension and uses cmake to build
the bundled flatc compiler.

Update the license information to cover the bundled LMDB, py-lmdb and
flatbuffers code.

Fixes: https://autobuild.buildroot.org/results/e3b026cb48f41ec531e5bdae9e07b8e581f1a06b

Changelog: https://github.com/crossbario/zlmdb/blob/master/docs/changelog.rst

Signed-off-by: Yegor Yefremov <yegorslists@googlemail.com>
Assisted-by: Claude:claude-opus-5-5
---
 package/python-zlmdb/Config.in         |  2 --
 package/python-zlmdb/python-zlmdb.hash |  7 ++++---
 package/python-zlmdb/python-zlmdb.mk   | 15 ++++++++++-----
 3 files changed, 14 insertions(+), 10 deletions(-)

diff --git a/package/python-zlmdb/Config.in b/package/python-zlmdb/Config.in
index 1edf993ecd..f6b8caebcb 100644
--- a/package/python-zlmdb/Config.in
+++ b/package/python-zlmdb/Config.in
@@ -9,8 +9,6 @@ config BR2_PACKAGE_PYTHON_ZLMDB
 	select BR2_PACKAGE_PYTHON_CBOR2 # runtime
 	select BR2_PACKAGE_PYTHON_CFFI # runtime
 	select BR2_PACKAGE_PYTHON_CLICK # runtime
-	select BR2_PACKAGE_PYTHON_FLATBUFFERS # runtime
-	select BR2_PACKAGE_PYTHON_LMDB # runtime
 	select BR2_PACKAGE_PYTHON_NUMPY # runtime
 	select BR2_PACKAGE_PYTHON_PYNACL # runtime
 	select BR2_PACKAGE_PYTHON_PYYAML # runtime
diff --git a/package/python-zlmdb/python-zlmdb.hash b/package/python-zlmdb/python-zlmdb.hash
index ed1b6db8c2..e29bbea280 100644
--- a/package/python-zlmdb/python-zlmdb.hash
+++ b/package/python-zlmdb/python-zlmdb.hash
@@ -1,5 +1,6 @@
 # md5, sha256 from https://pypi.org/pypi/zlmdb/json
-md5  4d96b46d1724b9d4cb6961874e5b4a9a  zlmdb-23.1.1.tar.gz
-sha256  ddcf680bf49352cabe35bfb5bfe3acbd5d6b8d481cafa508c423e0b18d654d05  zlmdb-23.1.1.tar.gz
+md5  186642d7df261a781631a734244f785e  zlmdb-26.7.1.tar.gz
+sha256  3cbc9447cfbf3b33dad0a30f7e671d467d72b41e5bc4e999b4f41914eff5fcb9  zlmdb-26.7.1.tar.gz
 # Locally computed sha256 checksums
-sha256  8a139bf325dcca11e0e476ce537bf791a6cfbeed8899a9b6ddc55238e180d230  LICENSE
+sha256  0ba0c0c595fd01ee19478ca417f210b75740f9b84ca937ebf783154e1cc01174  LICENSE
+sha256  cfc7749b96f63bd31c3c42b5c471bf756814053e847c10f3eb003417bc523d30  deps/flatbuffers/LICENSE
diff --git a/package/python-zlmdb/python-zlmdb.mk b/package/python-zlmdb/python-zlmdb.mk
index 70538ce63c..da625f9777 100644
--- a/package/python-zlmdb/python-zlmdb.mk
+++ b/package/python-zlmdb/python-zlmdb.mk
@@ -4,11 +4,16 @@
 #
 ################################################################################
 
-PYTHON_ZLMDB_VERSION = 23.1.1
+PYTHON_ZLMDB_VERSION = 26.7.1
 PYTHON_ZLMDB_SOURCE = zlmdb-$(PYTHON_ZLMDB_VERSION).tar.gz
-PYTHON_ZLMDB_SITE = https://files.pythonhosted.org/packages/56/b2/abaeb5419435a6224a0beb2b5edad621ec975fe4802297963ecf1728b883
-PYTHON_ZLMDB_SETUP_TYPE = setuptools
-PYTHON_ZLMDB_LICENSE = MIT
-PYTHON_ZLMDB_LICENSE_FILES = LICENSE
+PYTHON_ZLMDB_SITE = https://files.pythonhosted.org/packages/87/21/5b877e438d652f78bcf88aec83474b373f8ab1b98b6c0c5d47db3481d6b0
+PYTHON_ZLMDB_SETUP_TYPE = hatch
+PYTHON_ZLMDB_LICENSE = MIT, OLDAP-2.8 (bundled lmdb, py-lmdb), Apache-2.0 (bundled flatbuffers)
+PYTHON_ZLMDB_LICENSE_FILES = LICENSE deps/flatbuffers/LICENSE
+# cmake is used to build the bundled flatc compiler
+PYTHON_ZLMDB_DEPENDENCIES = \
+	$(BR2_CMAKE_HOST_DEPENDENCY) \
+	host-python-cffi \
+	host-python-setuptools
 
 $(eval $(python-package))
-- 
2.34.1

_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2026-10-13 14:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-13 14:04 [Buildroot] [PATCH 1/2] package/python-zlmdb: select python3 zlib support Yegor Yefremov via buildroot
2026-10-13 14:04 ` Yegor Yefremov [this message]
2026-10-13 21:12   ` [Buildroot] [PATCH 2/2] package/python-zlmdb: bump to version 26.7.1 Thomas Petazzoni via buildroot
2026-10-13 21:09 ` [Buildroot] [PATCH 1/2] package/python-zlmdb: select python3 zlib support Thomas Petazzoni via buildroot

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20261013140423.1941069-2-yegorslists@googlemail.com \
    --to=yegorslists@googlemail.com \
    --cc=buildroot@buildroot.org \
    --cc=james.hilliard1@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox