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 1/2] package/python-zlmdb: select python3 zlib support
Date: Tue, 13 Oct 2026 23:09:43 +0200 [thread overview]
Message-ID: <as6dzPRAfNnf8RNQ@windsurf> (raw)
In-Reply-To: <20261013140423.1941069-1-yegorslists@googlemail.com>
On Tue, Oct 13, 2026 at 04:04:22PM +0200, Yegor Yefremov via buildroot wrote:
> zlmdb/_pmap.py unconditionally imports the zlib module, so importing
> zlmdb fails without it:
>
> ModuleNotFoundError: No module named 'zlib'
>
> Select BR2_PACKAGE_PYTHON3_ZLIB.
>
> Signed-off-by: Yegor Yefremov <yegorslists@googlemail.com>
> Assisted-by: Claude:claude-opus-5-5
Usual request: when providing a fix, always include the information of
which commit introduced the problem. If it has been a problem since
the package was added, the Fixes: tag can point to the commit adding
the package.
Without this information, LTS maintainers will have to dig themselves
into this to figure out whether this fix needs to be backported or
not, and our LTS maintainers already have to crawl through hundreds of
commits, so let's make their life easier :)
Thanks!
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
prev parent reply other threads:[~2026-10-13 21:09 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
2026-10-13 21:09 ` Thomas Petazzoni via buildroot [this message]
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=as6dzPRAfNnf8RNQ@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