Bug 945864 – =dev-lang/python-3.12.8: ModuleNotFoundError: No module named 'gpep517'

• Status: UNCONFIRMED
• Product: Gentoo Linux

[Description tt_1 2024-12-04 14:17:27 UTC]

Created attachment 913299 [details]
compressed build.log including src install

hello, I just noticed a warning or error during install of =dev-lang/python-3.12.8: 

 * Verifying compiled files for python3.12
Traceback (most recent call last):
  File "/usr/lib/python-exec/python3.12/gpep517", line 3, in <module>
    from gpep517.__main__ import main
ModuleNotFoundError: No module named 'gpep517'


the python modules dev-python/gpep517-16 is available on my system

emerge -pv =dev-lang/python-3.12.8


[ebuild   R   ~] dev-lang/python-3.12.8:3.12::gentoo  USE="ensurepip gdbm ncurses readline sqlite ssl -bluetooth -build -debug -examples -libedit -pgo -test -tk -valgrind -verify-sig" 0 KiB

[Comment 1 tt_1 2024-12-04 14:19:36 UTC]

Created attachment 913300 [details]
output from emerge --info

[Comment 2 tt_1 2024-12-04 14:20:41 UTC]

the ebuild still merges, so I don't know if this is a problem at all

[Comment 3 cyberbat 2024-12-23 00:13:14 UTC]

I have also met the issue. 
I tried to install app-admin/ansible-core-2.18.1-r1 with some patches using 
ebuild ansible-core-2.18.1-r1.ebuild unpack
applying patches
ebuild ansible-core-2.18.1-r1.ebuild merge

and I have got the log:

cybernote /usr/portage/app-admin/ansible-core # ebuild ansible-core-2.18.1-r1.ebuild merge
>>> Existing ${T}/environment for 'ansible-core-2.18.1-r1' will be
>>> sourced. Run 'clean' to start with a fresh environment.
>>> Checking ansible_core-2.18.1.tar.gz's mtime...
>>> WORKDIR is up-to-date, keeping...
>>> It appears that 'pretend' has already executed for 'ansible-core-2.18.1-r1'; skipping.
>>> Remove '/var/tmp/portage/app-admin/ansible-core-2.18.1-r1/.pretended' to force pretend.
>>> It appears that 'setup' has already executed for 'ansible-core-2.18.1-r1'; skipping.
>>> Remove '/var/tmp/portage/app-admin/ansible-core-2.18.1-r1/.setuped' to force setup.
>>> It appears that 'unpack' has already executed for 'ansible-core-2.18.1-r1'; skipping.
>>> Remove '/var/tmp/portage/app-admin/ansible-core-2.18.1-r1/.unpacked' to force unpack.
>>> It appears that 'prepare' has already executed for 'ansible-core-2.18.1-r1'; skipping.
>>> Remove '/var/tmp/portage/app-admin/ansible-core-2.18.1-r1/.prepared' to force prepare.
>>> It appears that 'configure' has already executed for 'ansible-core-2.18.1-r1'; skipping.
>>> Remove '/var/tmp/portage/app-admin/ansible-core-2.18.1-r1/.configured' to force configure.
>>> Compiling source in /var/tmp/portage/app-admin/ansible-core-2.18.1-r1/work/ansible_core-2.18.1 ...
 * python3_12: running distutils-r1_run_phase distutils-r1_python_compile
/usr/bin/python3.12: No module named gpep517

emerging gpep517 fixes the issue

[Comment 4 Michał Górny 2024-12-23 05:48:24 UTC]

(In reply to cyberbat from comment #3)
> I have also met the issue. 
> I tried to install app-admin/ansible-core-2.18.1-r1 with some patches using 
> ebuild ansible-core-2.18.1-r1.ebuild unpack
> applying patches
> ebuild ansible-core-2.18.1-r1.ebuild merge
> 

That is not the same problem.  When you're calling ebuild(1), you're not getting dependencies installed.  I've just (unnecessarily) verified that the ansible-core ebuild has correct dependencies.