From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: "Raphaël Mélotte" <raphael.melotte@mind.be>
Cc: buildroot@buildroot.org, James Hilliard <james.hilliard1@gmail.com>
Subject: Re: [Buildroot] [PATCH 2/2] package/mupdf, python-pymupdf: bump to versions 1.28.5 and 1.28.2
Date: Sun, 4 Oct 2026 17:41:07 +0200 [thread overview]
Message-ID: <asJzHhtAaiN13HMS@windsurf> (raw)
In-Reply-To: <20260930120101.474560-2-raphael.melotte@mind.be>
Hello Raphaël,
Wow, lots of work here. mupdf seems pretty crazy to build, and their
usage of clang doesn't seem to be making things simple. Do you expect
some/all of your patches to be merged?
More comments below (not many).
On Wed, Sep 30, 2026 at 02:00:58PM +0200, Raphaël Mélotte via buildroot wrote:
> Release notes:
> https://mupdf.com/releases
> https://pymupdf.readthedocs.io/en/latest/changes.html
>
> Note that this bump fixes multiple security vulnerabilities, and at
> least the following ones:
> - CVE-2025-46206
> - CVE-2025-71382
> - CVE-2026-7233
> - CVE-2026-40505
So should this commit be title "security bump to ..." ?
> select BR2_PACKAGE_HOST_SWIG
> select BR2_PACKAGE_FREETYPE
> select BR2_PACKAGE_MUPDF
> + select BR2_PACKAGE_MUPDF_PYTHON_BINDINGS
> + select BR2_PACKAGE_PYTHON_PIPCL
As I reported in my review of the previous patch, this option exists
but doesn't do anything as python-pipcl doesn't exist as a target
package. I assume this can be dropped?
Thanks for your feedback!
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
next prev parent reply other threads:[~2026-10-04 15:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-30 12:00 [Buildroot] [PATCH 1/2] package/python-pipcl: new host package Raphaël Mélotte via buildroot
2026-09-30 12:00 ` [Buildroot] [PATCH 2/2] package/mupdf, python-pymupdf: bump to versions 1.28.5 and 1.28.2 Raphaël Mélotte via buildroot
2026-10-01 5:52 ` Waldemar Brodkorb
2026-10-04 15:41 ` Thomas Petazzoni via buildroot [this message]
2026-10-05 12:47 ` Raphaël Mélotte via buildroot
2026-10-05 15:50 ` Thomas Petazzoni via buildroot
2026-10-07 10:46 ` Raphaël Mélotte via buildroot
2026-10-04 15:38 ` [Buildroot] [PATCH 1/2] package/python-pipcl: new host package Thomas Petazzoni via buildroot
2026-10-05 12:39 ` Raphaël Mélotte via buildroot
2026-10-05 15:40 ` [Buildroot] [PATCH v2 " Raphaël Mélotte via buildroot
2026-10-05 15:40 ` [Buildroot] [PATCH v2 2/2] package/mupdf, python-pymupdf: bump to versions 1.28.5 and 1.28.2 Raphaël Mélotte 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=asJzHhtAaiN13HMS@windsurf \
--to=buildroot@buildroot.org \
--cc=james.hilliard1@gmail.com \
--cc=raphael.melotte@mind.be \
--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