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

On Tue, Oct 13, 2026 at 04:04:23PM +0200, Yegor Yefremov wrote:
> 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

When was the problem introduced? I.e does the problem exist in
2025.02.x?

It's always a bit annoying to have to do a major bump to fix an issue,
as it's more risk in terms of backporting to an LTS branch;

Thomas
-- 
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2026-10-13 21:12 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 ` [Buildroot] [PATCH 2/2] package/python-zlmdb: bump to version 26.7.1 Yegor Yefremov
2026-10-13 21:12   ` Thomas Petazzoni via buildroot [this message]
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=as6eHGluGeyQ9GSt@windsurf \
    --to=buildroot@buildroot.org \
    --cc=james.hilliard1@gmail.com \
    --cc=thomas.petazzoni@bootlin.com \
    --cc=yegorslists@googlemail.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