From patchwork Wed Aug 5 05:47:31 2026 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: auh@yoctoproject.org X-Patchwork-Id: 94565 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from aws-us-west-2-korg-lkml-1.web.codeaurora.org (localhost.localdomain [127.0.0.1]) by smtp.lore.kernel.org (Postfix) with ESMTP id 09ACAC56203 for ; Wed, 5 Aug 2026 05:47:42 +0000 (UTC) Received: from a27-191.smtp-out.us-west-2.amazonses.com (a27-191.smtp-out.us-west-2.amazonses.com [54.240.27.191]) by mx.groups.io with SMTP id smtpd.msgproc02-g2.34096.1785908851757861402 for ; Tue, 04 Aug 2026 22:47:31 -0700 Authentication-Results: mx.groups.io; dkim=pass header.i=@yoctoproject.org header.s=lvjh2tk576v2ro5mi6k4dt3mc6wpqbky header.b=pmdWNZ3w; dkim=pass header.i=@amazonses.com header.s=hsbnp7p3ensaochzwyq5wwmceodymuwv header.b=cQG8sB98; spf=pass (domain: us-west-2.amazonses.com, ip: 54.240.27.191, mailfrom: 0101019fd0767130-704010f2-be50-4e85-a2f0-13bce4b70154-000000@us-west-2.amazonses.com) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple; s=lvjh2tk576v2ro5mi6k4dt3mc6wpqbky; d=yoctoproject.org; t=1785908851; h=Content-Type:MIME-Version:From:To:Cc:Subject:Message-Id:Date; bh=PkGMful15dz+h8jRcFwNun14Wp2L5XDbm9lCmgwMJ6M=; b=pmdWNZ3wGgUg93ApfLW4h+vS5MQ3GBJzwQx62poGx04G12BWsQl/b+eyjY8n5bq0 yLIuiCYgxdky9NmDW+Pe+Zxwop3ySiQABA7DfDlcv7hKZt/Zmp2gVUamszVRG050xMi GObynVSEfRgQQsNaiebGf3qpTwJbp1GLQWNm6t8M= DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple; s=hsbnp7p3ensaochzwyq5wwmceodymuwv; d=amazonses.com; t=1785908851; h=Content-Type:MIME-Version:From:To:Cc:Subject:Message-Id:Date:Feedback-ID; bh=PkGMful15dz+h8jRcFwNun14Wp2L5XDbm9lCmgwMJ6M=; b=cQG8sB98vum8b8p5WcWlfuOUOy6qhn8xweKGbznImq0MYEQ1eIs6sPN69ZwVFExs 5lycvOD6QXFzOqCAuqJJLCZ0DQdHtuINx9tbMFddodTcZzm6jjN66f1pWs4pG/Y5kVi 3nmq86BFI7oum6wCSrcu3sdXJQrOlZIynk9qmuT0= MIME-Version: 1.0 From: auh@yoctoproject.org To: Tim Orling Cc: openembedded-core@lists.openembedded.org Subject: [AUH] python3-flit-core: upgrading to 4.0.2 FAILED Message-ID: <0101019fd0767130-704010f2-be50-4e85-a2f0-13bce4b70154-000000@us-west-2.amazonses.com> Date: Wed, 5 Aug 2026 05:47:31 +0000 Feedback-ID: ::1.us-west-2.9np3MYPs3fEaOBysGKSlUD4KtcmPijcmS9Az2Hwf7iQ=:AmazonSES X-SES-Outgoing: 2026.08.05-54.240.27.191 List-Id: X-Webhook-Received: from 45-33-107-173.ip.linodeusercontent.com [45.33.107.173] by aws-us-west-2-korg-lkml-1.web.codeaurora.org with HTTPS for ; Wed, 05 Aug 2026 05:47:42 -0000 X-Groupsio-URL: https://lists.openembedded.org/g/openembedded-core/message/242814 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 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 ` 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 ` 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