From: Julien Olivain via buildroot <buildroot@buildroot.org>
To: Daniel Houck <Software@drhouck.me>
Cc: buildroot@buildroot.org, Chris Packham <judge.packham@gmail.com>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Subject: Re: [Buildroot] [PATCH v2 1/1] package/micropython: bump to version 1.28.0
Date: Fri, 12 Jun 2026 22:02:20 +0200 [thread overview]
Message-ID: <5ab2ee2829ff2f40bb249c1d1d539018@free.fr> (raw)
In-Reply-To: <20260601083827.2545221-1-Software@DRHouck.me>
On 01/06/2026 10:38, Daniel Houck wrote:
> This allows us to fix packaging issue with micropython-lib, which was
> not packaging the correct versions of some libraries. The new version
> makes changes to the `manifestfile` tool/library used by our
> collect_micropython_libs.py script, which makes it easier to collect
> the
> correct library version. This fixes #166.
>
> To better support alternate use cases, the option to package the
> modules
> in unix-ffi has been split into a separate option, instead of assuming
> it's needed if and only if libffi is selected.
>
> Both the upstream changes and the unix-ffi split require changes to
> collect_micropython_libs.py. First, since we might not want the
> unix-ffi libraries, the script takes an extra argument for whether or
> not to include them. Next, since the manifest.require function no
> longer takes a unix_ffi optional parameter, we use manifest.add_library
> as recommended in the micropython-lib/unix-ffi directory README, if we
> are are actually packaging those libraries.
>
> All of the patches we have been maintaining have also been merged
> upstream
> by 1.28.0, so they are removed. Their respective Upstream: trailers
> all
> point to the relevant commits, except for
> 0003-Fixes-for-GCC-15-1-unterminated-string-literal-warning.patch, from
> https://github.com/micropython/micropython/commit/ae6062a45a776e193e8c02ece62d058b64f2b4f5
>
> The LICENSE hash has been updated, as the year and the licenses used
> for
> the ports and libraries have also been updated in the LICENSE file.
>
> For more details on the version bump, see the release notes:
> - https://github.com/micropython/micropython/releases/tag/v1.23.0
> - https://github.com/micropython/micropython/releases/tag/v1.24.0
> - https://github.com/micropython/micropython/releases/tag/v1.24.1
> - https://github.com/micropython/micropython/releases/tag/v1.25.0
> - https://github.com/micropython/micropython/releases/tag/v1.26.0
> - https://github.com/micropython/micropython/releases/tag/v1.26.1
> - https://github.com/micropython/micropython/releases/tag/v1.27.0
> - https://github.com/micropython/micropython/releases/tag/v1.28.0
>
> Signed-off-by: Daniel Houck <Software@DRHouck.me>
Applied to master, thanks.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2026-06-12 20:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-08 23:52 [Buildroot] [PATCH 1/1] package/micropython: bump to version 1.28.0 Daniel Houck
2026-05-30 21:27 ` Thomas Petazzoni via buildroot
2026-06-01 0:25 ` Daniel Houck
2026-06-01 7:23 ` Thomas Petazzoni via buildroot
2026-06-01 8:38 ` [Buildroot] [PATCH v2 " Daniel Houck
2026-06-12 20:02 ` Julien Olivain 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=5ab2ee2829ff2f40bb249c1d1d539018@free.fr \
--to=buildroot@buildroot.org \
--cc=Software@drhouck.me \
--cc=ju.o@free.fr \
--cc=judge.packham@gmail.com \
--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