SOLVED python 3.12 fontforge No module named 'distutils'

[logrusx]

I'm running update to python 3.12, 59 packages aside from the 154 reported are already emerged.

https://bpa.st/ABXA

Is this something related to the python update or a separate issue?

p.s. pay attention to the title, shorten or remove it when you replay or you'll get an error posting.

Best Regards,
Georgi

[sam_]

Yeah, it's a bug in fontforge. Please file one on bugs.gentoo.org. We need to pull in https://github.com/fontforge/fontforge/pull/5423[b][/b].

[logrusx]

Thanks Sam! I see you're already on it, but for the record: https://bugs.gentoo.org/933392

Best Regards,
Georgi

[sam_]

Thank you!

[lefou]

Looks like installation of media-libs/vigra-1.11.1-r9:0 with Python 3.12 suffers from the same issue.

Code: Select all

-- Checking VIGRANUMPY_DEPENDENCIES
-- Using Python 3.12.3 at /var/tmp/portage/media-libs/vigra-1.11.1-r9/temp/python3.12/bin/python
Traceback (most recent call last):
  File "<string>", line 1, in <module>
ModuleNotFoundError: No module named 'distutils'
-- Could NOT find Python includes
Traceback (most recent call last):
  File "<string>", line 1, in <module>
ModuleNotFoundError: No module named 'distutils'
Traceback (most recent call last):
  File "<string>", line 1, in <module>
ModuleNotFoundError: No module named 'distutils'
-- Could NOT find Python library
-- Found boost_python library: /usr/lib64/libboost_python312.so
Traceback (most recent call last):
  File "<string>", line 1, in <module>
ModuleNotFoundError: No module named 'distutils'
CMake Error at config/FindVIGRANUMPY_DEPENDENCIES.cmake:146 (FILE):
  FILE FILE([TO_CMAKE_PATH|TO_NATIVE_PATH] path result) must be called with
  exactly three arguments.
Call Stack (most recent call first):
  CMakeLists.txt:189 (FIND_PACKAGE)


CMake Error at config/FindVIGRANUMPY_DEPENDENCIES.cmake:152 (FILE):
  FILE RELATIVE_PATH called with incorrect number of arguments
Call Stack (most recent call first):
  CMakeLists.txt:189 (FIND_PACKAGE)


Traceback (most recent call last):
  File "<string>", line 1, in <module>
ModuleNotFoundError: No module named 'numpy.distutils'
-- Could NOT find Python numpy ('import numpy.distutils.misc_util' failed)
Traceback (most recent call last):
  File "<string>", line 1, in <module>
ModuleNotFoundError: No module named 'nose'

[lefou]

Looks like I could "fix" it by forcing the installation of dev-python/setuptools with --nodeps.

[logrusx]

Looks like I could "fix" it by forcing the installation of dev-python/setuptools with --nodeps.

It only looks that way: https://bugs.gentoo.org/929649

First, when you have such a problem you file a bug. You don't hijack a threads, especially if it's marked solved. It may not attract attention to your problem. Open a new thread.

Now about the issue. Portage dependency graph only reflects dependencies between packages. It'll only tell you if a package is going to compile. If you force it to disregard it's own dependency database, it won't magically satisfy a package's dependencies. It'll just tell you "OK, I give up, you're in charge whatever happens" and will start the compilation. If it succeeds with unsatisfied dependencies, that's a bug. Somewhere unnecessary dependency is declared. However this was not the case. You just synced shortly after astrum's commit.

Best Regards,
Georgi

[sam_]

I think there might be a genuine issue left with vigra. I'll look now.

[logrusx]

I think there might be a genuine issue left with vigra. I'll look now.

Thanks for checking in. However I don't see how --nodeps would solve the original issue. If it did without the ebuild changing, it would have been a bug.

Best Regards,
Georgi

[lefou]

I used --nodeps to install setuptools since that is the package that provided the distutils application. I think vigra was about to be installed as part of a Python 3.11 -> 3.12 update, and the setuptools package wasn't already merged for the newer Python version. Could be an undeclared build time dependency?

Sorry for hijacking the solved topic.

[sam_]

You're both right.

The issue at hand is that distutils was removed from Python 3.12 (it used to be in the stdlib), but setuptools can provide it as a compatibility hack for now. So, the ebuild either has to depend on setuptools (technically just for >=py3.12), or patch out the use of distutils. I went for the latter. Thank you!

[logrusx]

I used --nodeps to install setuptools since that is the package that provided the distutils application. I think vigra was about to be installed as part of a Python 3.11 -> 3.12 update, and the setuptools package wasn't already merged for the newer Python version. Could be an undeclared build time dependency?

Sorry, I missed you mentioned setuptools. I have the tendency to miss tings :)

So both our concerns were addressed by Sam.

Thank you Sam!

Sorry for hijacking the solved topic. :oops:

I don't mind and I might not have had to use the word hijacking. Since English is not my first language, I often don't think of how strong a word sounds and also its other meanings. To me it's just a term, while it bears certain negative charge in English, which is a bit too strong for the situation. My main concern was it's a better way to get help to open a new thread with the particular issue at hand.

Best Regards,
Georgi