Bug 2155047 - lnst fails to build with Python 3.12: ModuleNotFoundError: No module named 'distutils'
Summary: lnst fails to build with Python 3.12: ModuleNotFoundError: No module named '...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: lnst
Version: 38
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Orphan Owner
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: PYTHON3.12
TreeView+ depends on / blocked
 
Reported: 2022-12-19 18:50 UTC by Tomáš Hrnčiar
Modified: 2024-05-21 14:23 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2024-05-21 14:23:53 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Tomáš Hrnčiar 2022-12-19 18:50:40 UTC
lnst fails to build with Python 3.12.0a3.

+ /usr/bin/python3 setup.py build
/builddir/build/BUILD/lnst-15/setup.py:29: SyntaxWarning: invalid escape sequence '\.'
  template_name_re = "\.in$"
Traceback (most recent call last):
  File "/builddir/build/BUILD/lnst-15/setup.py", line 25, in <module>
    from distutils.core import setup
ModuleNotFoundError: No module named 'distutils'

Remove the distutils package. It was deprecated in Python 3.10 by PEP 632 “Deprecate distutils module”. For projects still using distutils and cannot be updated to something else, the setuptools project can be installed: it still provides distutils. (Contributed by Victor Stinner in gh-92584.)

If your package is listed in [0], you may workaround this issue by BuildRequiring python-setuptools, note that adding such BuildRequires might however hide some transitive dependency problem, if the distutils import comes from a dependency.
Cooperation with upstream is recommended. Additional context [1].

[0] https://lists.fedoraproject.org/archives/list/python-devel@lists.fedoraproject.org/message/6BHNAWHE7M5VY3YQVJLOYHLY4M7KIFFN/

[1] https://lists.fedoraproject.org/archives/list/python-devel@lists.fedoraproject.org/thread/N6ITYHLRWIDNYNXGPYG2ZHF3ZLQWZN7L/

https://docs.python.org/3.12/whatsnew/3.12.html

For the build logs, see:
https://copr-be.cloud.fedoraproject.org/results/@python/python3.12/fedora-rawhide-x86_64/05128078-lnst/

For all our attempts to build lnst with Python 3.12, see:
https://copr.fedorainfracloud.org/coprs/g/python/python3.12/package/lnst/

Testing and mass rebuild of packages is happening in copr. You can follow these instructions to test locally in mock if your package builds with Python 3.12:
https://copr.fedorainfracloud.org/coprs/g/python/python3.12/

Let us know here if you have any questions.

Python 3.12 is planned to be included in Fedora 39. To make that update smoother, we're building Fedora packages with all pre-releases of Python 3.12.
A build failure prevents us from testing all dependent packages (transitive [Build]Requires), so if this package is required a lot, it's important for us to get it fixed soon.
We'd appreciate help from the people who know this package best, but if you don't want to work on this now, let us know so we can try to work around it on our side.

Comment 1 Ondrej Lichtner 2023-01-05 13:46:45 UTC
Hi,

while we've kept the package rpm "alive" for the past while, we've kept it at a very old version that we now consider deprecated legacy.

The upstream project was refactored and is incompatible with this older version and we've also moved on to using poetry for dependency and installation handling. We currently don't have a plan or desire to update this rpm to this newer version of the project or to create a new rpm package for it either.

We don't see much use in keeping this rpm around anymore and would like to basically deprecated it or remove the rpm completely if that is possible.

This would of course include the removal of the dependent packages: lnst-ctl, lnst-slave and lnst-recipes.

What do we need to do to achieve this?

-Ondrej

Comment 2 Miro Hrončok 2023-01-05 15:28:56 UTC
The package seems to be self-contained (all the dependents are subpackages of it). I recommend orphaning it, follow https://docs.fedoraproject.org/en-US/package-maintainers/Package_Orphaning_Process/#orphaning_procedure

Comment 3 Ondrej Lichtner 2023-01-06 12:45:35 UTC
done, thanks.

So I should now reassign this bug to the orphan user as well?

-Ondrej

Comment 4 Miro Hrončok 2023-01-06 12:47:02 UTC
It should happen automatically in ~1 day, but no harm in doing so right away.

Comment 5 Ben Cotton 2023-02-07 15:03:06 UTC
This bug appears to have been reported against 'rawhide' during the Fedora Linux 38 development cycle.
Changing version to 38.

Comment 6 Aoife Moloney 2024-05-07 15:54:05 UTC
This message is a reminder that Fedora Linux 38 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 38 on 2024-05-21.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '38'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 38 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 7 Aoife Moloney 2024-05-21 14:23:53 UTC
Fedora Linux 38 entered end-of-life (EOL) status on 2024-05-21.

Fedora Linux 38 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of Fedora Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.


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