Bug 2378038 - python-pyghmi: Stop using deprecated %py3_build/%py3_install macros
Summary: python-pyghmi: Stop using deprecated %py3_build/%py3_install macros
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: python-pyghmi
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Dmitry Tantsur
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: 2376118
TreeView+ depends on / blocked
 
Reported: 2025-07-08 14:58 UTC by Miro Hrončok
Modified: 2025-07-20 22:13 UTC (History)
2 users (show)

Fixed In Version: python-pyghmi-1.6.2-1.fc43
Clone Of:
Environment:
Last Closed: 2025-07-08 15:33:40 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Miro Hrončok 2025-07-08 14:58:13 UTC
Dear package maintainer,

this bugzilla is automated becasue the number of impacted packages it too high to go trough manually.


It appears that your package uses the deprecated %py3_build and/or %py3_install macro.

See https://fedoraproject.org/wiki/Changes/DeprecateSetuppyMacros for why the macros are deprecated.

%py3_install expands to python setup.py install. This has been a deprecated command for 5 years and will likely stop working in Fedora 45.



Please migrate to %pyproject_buildrequires + %pyproject_wheel + %pyproject_install macros instead.

See https://fedoraproject.org/wiki/Changes/DeprecateSetuppyMacros#Migrating_to_%pyproject_macros for migration guide.

See https://github.com/hroncok/pyprojectize/ for a tool that can help you automate the migration.


Thank you. Let me know if you need help.

Comment 1 Dmitry Tantsur 2025-07-08 15:33:40 UTC
> This has been a deprecated command for 5 years and will likely stop working in Fedora 45.

Note that this depends on upstream, not me. I think they still support Python 2 for some reason...

Switched to new macros in 1.6.2-1

Comment 2 Miro Hrončok 2025-07-08 15:39:54 UTC
> Note that this depends on upstream, not me.

I don't really understand this comment. It depend on what's written in the specfile.

Anyway, thanks for the fix.

Comment 3 Dmitry Tantsur 2025-07-20 15:09:08 UTC
> I don't really understand this comment. It depend on what's written in the specfile.

Sorry, I meant: upstream does not support the new tooling, so even with new macros, it's still `python setup.py` and setuptools under the hood.

And since they still support 2.7, I don't know if they'll be willing to migrate any soon.

Comment 4 Miro Hrončok 2025-07-20 22:13:37 UTC
The new tooling is designed to support using setuptools under the hood. The point is that the setup.py file is not used to call "setup.py install" as a command anymore (not even under the hood).

There is no need for upstream to migrate anywhere; everything is fine as it is here.


Note You need to log in before you can comment on or make changes to this bug.