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: Mon, 5 Oct 2026 17:50:14 +0200 [thread overview]
Message-ID: <asPHCM2j8FJcUQgn@windsurf> (raw)
In-Reply-To: <bf405ebf-ba9f-4033-8150-a5069ad151bb@mind.be>
On Mon, Oct 05, 2026 at 02:47:37PM +0200, Raphaël Mélotte wrote:
> I still hope they will be eventually (at least the ones that fix
> build issues), but given that some of them are more than a year old
> I'm also not that confident they will be unfortunately.
Meh :-/
> > So should this commit be title "security bump to ..." ?
>
> I did not use it because our documentation says to use it "If the
> new version only contains security updates compared to the existing
> one". In this case it's a bump across several major releases, so it
> definitely contains more than security updates.
And is it possible to backport just the security fixes? Otherwise our
LTS maintainers will have no choice but to bump the version, but you
said yourself that this should be considered very carefully.
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-05 15:59 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
2026-10-05 12:47 ` Raphaël Mélotte via buildroot
2026-10-05 15:50 ` Thomas Petazzoni via buildroot [this message]
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=asPHCM2j8FJcUQgn@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