Re: [OE-core][PATCH v2] python3-roman-numerals-py: upgrade 3.1.0 -> 4.1.0

[Paul Barker <paul@pbarker.dev>]

[-- Attachment #1: Type: text/plain, Size: 1392 bytes --]

On Thu, 2026-01-08 at 09:41 +0800, Yiding Liu (Fujitsu) via
lists.openembedded.org wrote:
> 1.Changelog:
>   Restore LICENCE.rst in the roman-numerals-py meta-package
>   Add some debug assertions for unsafe blocks
> 
> 2.Add bbclass python_setuptools_build_meta to solve following error:
>   pyproject_hooks._impl.BackendUnavailable: Cannot import 'setuptools.build_meta'
>   ERROR Backend 'setuptools.build_meta' is not available.

Thanks for adding the extra info.

However, this doesn't explain why we now need the setuptools.build_meta
backend, we should say what upstream change caused this. This caused me
to look at the upstream v4.0.0 release notes and I found:

  - Rename Python package to roman-numerals on PyPI.
  - Publish roman-numerals-py as a meta-package that depends on
    roman-numerals and installs no modules.

So I'm not sure we can take the new version as-is, the roman-numerals-py
package is now empty.

It looks like this recipe is here to support python3-sphinx, have you
tested that still works after this update?

As a side note, when we upgrade a recipe across multiple upstream
versions we should include the changelog entries in our commit message
for each version we skip across, especially if there's a major version
bump in there as it's often because of some backwards incompatibility.

Best regards,

-- 
Paul Barker


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 252 bytes --]