Several consumers are not yet ready for flit_core 4.x (range is limited to < 4 in pyproject.toml etc.):
python3-pyparsing_3.3.2.bb python3-typing-extensions_4.16.0.bb python3-jinja2_3.1.6.bb python3-wheel_0.47.0.bb On Tue, Aug 4, 2026 at 10:47 PM <[email protected]> wrote: > Hello, > > this email is a notification from the Auto Upgrade Helper > that the automatic attempt to upgrade the recipe(s) *python3-flit-core* to > *4.0.2* has Failed(do_compile). > > Detailed error information: > > do_compile failed > > > > Next steps: > - apply the patch: git am > 0001-python3-flit-core-upgrade-3.12.0-4.0.2.patch > - check the changes to upstream patches and summarize them in the > commit message, > - compile an image that contains the package > - perform some basic sanity tests > - amend the patch and sign it off: git commit -s --reset-author --amend > - send it to the appropriate mailing list > > Alternatively, if you believe the recipe should not be upgraded at this > time, > you can fill RECIPE_NO_UPDATE_REASON in respective recipe file so that > automatic upgrades would no longer be attempted. > > Please review the attached files for further information and build/update > failures. > Any problem please file a bug at > https://bugzilla.yoctoproject.org/enter_bug.cgi?product=Automated%20Update%20Handler > > Regards, > The Upgrade Helper > > -- >8 -- > From cb3320ee18367f0609f7640100a8951159c3e75e Mon Sep 17 00:00:00 2001 > From: Upgrade Helper <[email protected]> > Date: Wed, 5 Aug 2026 05:12:58 +0000 > Subject: [PATCH] python3-flit-core: upgrade 3.12.0 -> 4.0.2 > > Source: doc/history.rst > > Version 4.0.2 > ------------- > > - Fix invalid metadata files with ``Import-Name`` (:ghissue:`813`). > > Version 4.0.1 > ------------- > > No changes, but a new tag to trigger an upload to PyPI now that twine will > accept it. > > Version 4.0 > ----------- > > This version contains breaking changes, but most projects which are already > using the ``[project]`` table for metadata shouldn't be affected, and can > simply > change the ``flit_core <4`` constraint to ``<5``. > > - The ``[tool.flit.metadata]`` table is no longer used for project metadata > (:ghpull:`771`). Use the newer :ref:`[project] table > <pyproject_toml_project>` > instead (or if that is not possible, build with ``flit_core <4``). > - :ref:`build_cmd` and :ref:`publish_cmd` no longer include files in the > sdist > based on what is committed in git or Mercurial (:ghpull:`772`). These > commands > now build packages more like Flit does when called as a backend by e.g. > ``python -m build``. Specify :ref:`sdist include & exclude patterns > <pyproject_toml_sdist>` instead (Flit can help to generate these), or > pass > the ``--use-vcs`` option to get the old behaviour back. > - ``flit_core`` now requires Python 3.8 or above (:ghpull:`738`) > - The ``--setup-py`` option to generate sdists containing a ``setup.py`` > file > is no longer available (:ghpull:`776`). > - Making typing stubs packages with a ``-stubs`` suffix will now work > (:ghpull:`742`). > - The default glob patterns for license files have been extended to include > ``NOTICE*`` and ``AUTHORS*`` (:ghpull:`758`). > - ``license-files`` glob patterns can contain spaces (:ghpull:`797`). > - Fix a bug where license files could be found twice on Windows > (:ghpull:`752`). > - The new ``Import-Name`` and ``Import-Namespace`` metadata fields > (metadata 2.5) > are now supported (:ghpull:`774`). In most cases no new input is > required, > as Flit will create this metadata automatically. > - Fix creating RECORD files when file names include commas (:ghpull:`744`). > - The ``--use-vcs`` option now correctly recognises git from inside a git > worktree folder (:ghpull:`799`). > - On Python 3.12 and above, ``flit build`` now uses the 'data' filter when > extracting the just-created sdist prior to building a wheel > (:ghpull:`775`). > This restricts some special features of tar files, but sdists are > unlikely > to use these features, and they would probably break in other scenarios > if > you did. > - The vendorised ``readme_renderer`` package was updated to version 44.0 > (:ghpull:`760`). > > - Flit will work with current development versions of Python again > (:ghpull:`684`). > - The ``flit`` command line package now requires Python 3.8 or above > (:ghpull:`660`). > - Flit now has a ``SECURITY.md`` file in the GitHub repository > (:ghpull:`665`). > new ``[tool.flit.metadata.urls]`` section of > archive, such as from GitHub. > --- > .../{python3-flit-core_3.12.0.bb => python3-flit-core_4.0.2.bb} | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > rename meta/recipes-devtools/python/{python3-flit-core_3.12.0.bb => > python3-flit-core_4.0.2.bb} (91%) > > diff --git a/meta/recipes-devtools/python/python3-flit-core_3.12.0.bb > b/meta/recipes-devtools/python/python3-flit-core_4.0.2.bb > similarity index 91% > rename from meta/recipes-devtools/python/python3-flit-core_3.12.0.bb > rename to meta/recipes-devtools/python/python3-flit-core_4.0.2.bb > index e40ffd0d0f..27aaae085d 100644 > --- a/meta/recipes-devtools/python/python3-flit-core_3.12.0.bb > +++ b/meta/recipes-devtools/python/python3-flit-core_4.0.2.bb > @@ -8,7 +8,7 @@ BUGTRACKER = "https://github.com/pypa/flit/issues"; > LICENSE = "BSD-3-Clause" > LIC_FILES_CHKSUM = "file://LICENSE;md5=41eb78fa8a872983a882c694a8305f08" > > -SRC_URI[sha256sum] = > "1c80f34dd96992e7758b40423d2809f48f640ca285d0b7821825e50745ec3740" > +SRC_URI[sha256sum] = > "232bc4317279e8952eca9fb3f5e000d8395d693b39c105b99f619ce461e1da85" > > inherit pypi python_flit_core > > -- > 2.47.1 > >
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#242871): https://lists.openembedded.org/g/openembedded-core/message/242871 Mute This Topic: https://lists.openembedded.org/mt/120606453/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
