From: Yegor Yefremov <yegorslists@googlemail.com>
To: buildroot@buildroot.org
Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Subject: [Buildroot] [PATCH v2 2/3] package/python-zlmdb: don't install the vendored flatbuffers package
Date: Wed, 14 Oct 2026 23:10:48 +0200 [thread overview]
Message-ID: <20261014211049.490297-2-yegorslists@gmail.com> (raw)
In-Reply-To: <20261014211049.490297-1-yegorslists@gmail.com>
From: Yegor Yefremov <yegorslists@googlemail.com>
zlmdb installs a copy of the flatbuffers runtime as a top-level
"flatbuffers" package, which conflicts with python-flatbuffers that
python-zlmdb selects:
FileExistsError: File already exists: .../target/usr/lib/python3.14/site-packages/flatbuffers/__init__.py
The overlap has been there since the package was added, but it became
fatal when setuptools packages were migrated to the pep517 installer,
which refuses to overwrite files.
Add a patch so that zlmdb doesn't install its copy and uses
python-flatbuffers instead.
Fixes: https://autobuild.buildroot.org/results/e3b026cb48f41ec531e5bdae9e07b8e581f1a06b
Fixes: 8937db8dd595 ("package/pkg-python.mk: migrate setuptools to pep517")
Signed-off-by: Yegor Yefremov <yegorslists@googlemail.com>
Assisted-by: Claude:claude-opus-5-5
---
Changes v1 -> v2:
- new patch: minimal fix for the flatbuffers conflict that can be
backported to the LTS branches instead of the version bump
(suggested by Thomas). Tested on master and 2025.02.x.
...all-the-vendored-flatbuffers-package.patch | 37 +++++++++++++++++++
1 file changed, 37 insertions(+)
create mode 100644 package/python-zlmdb/0001-setup.py-don-t-install-the-vendored-flatbuffers-package.patch
diff --git a/package/python-zlmdb/0001-setup.py-don-t-install-the-vendored-flatbuffers-package.patch b/package/python-zlmdb/0001-setup.py-don-t-install-the-vendored-flatbuffers-package.patch
new file mode 100644
index 0000000000..608074ea51
--- /dev/null
+++ b/package/python-zlmdb/0001-setup.py-don-t-install-the-vendored-flatbuffers-package.patch
@@ -0,0 +1,37 @@
+From 18c4d2d3c7c0c3104e9280ea717c68a5d8f1368d Mon Sep 17 00:00:00 2001
+From: Yegor Yefremov <yegorslists@googlemail.com>
+Date: Wed, 14 Oct 2026 17:52:45 +0200
+Subject: [PATCH] setup.py: don't install the vendored flatbuffers package
+
+zlmdb installs a copy of the flatbuffers runtime as a top-level
+"flatbuffers" package, although it also depends on the flatbuffers
+package (install_requires). Both install
+site-packages/flatbuffers/__init__.py, so installing zlmdb on top of
+flatbuffers fails with a pep517 installer:
+
+ FileExistsError: File already exists: .../site-packages/flatbuffers/__init__.py
+
+Don't install the vendored copy and use the flatbuffers package
+instead. zlmdb.flatbuffers (the reflection code) is not affected.
+
+Upstream: N/A, since version 25.12.1 upstream no longer installs a
+top-level flatbuffers package (the runtime is vendored as
+zlmdb.flatbuffers).
+
+Signed-off-by: Yegor Yefremov <yegorslists@googlemail.com>
+---
+ setup.py | 1 -
+ 1 file changed, 1 deletion(-)
+
+diff --git a/setup.py b/setup.py
+index 16ed0cb..571615a 100644
+--- a/setup.py
++++ b/setup.py
+@@ -67,7 +67,6 @@ with open('requirements-dev.txt') as f:
+ test_requirements = ['pytest', 'pytest-runner']
+
+ packages = [
+- 'flatbuffers',
+ 'zlmdb',
+ 'zlmdb.flatbuffers',
+ 'zlmdb.flatbuffers.reflection',
--
2.34.1
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2026-10-14 21:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-14 21:10 [Buildroot] [PATCH v2 1/3] package/python-zlmdb: select python3 zlib support Yegor Yefremov
2026-10-14 21:10 ` Yegor Yefremov [this message]
2026-10-14 21:10 ` [Buildroot] [PATCH v2 3/3] package/python-zlmdb: bump to version 26.7.1 Yegor Yefremov
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=20261014211049.490297-2-yegorslists@gmail.com \
--to=yegorslists@googlemail.com \
--cc=buildroot@buildroot.org \
--cc=thomas.petazzoni@bootlin.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