Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 821619 - sys-apps/portage-3.0.28 emerging fails with "No module named 'sphinx_epytext'"
Summary: sys-apps/portage-3.0.28 emerging fails with "No module named 'sphinx_epytext'"
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal
Assignee: Portage team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-11-04 07:48 UTC by Florian Schmaus
Modified: 2021-11-04 21:54 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments
build.log (build.log,286.32 KB, text/plain)
2021-11-04 07:48 UTC, Florian Schmaus
Details
emerge --info (emerge-info.txt,7.51 KB, text/plain)
2021-11-04 07:48 UTC, Florian Schmaus
Details
emerge -pqv portage (emerge-pqv.txt,210 bytes, text/plain)
2021-11-04 07:49 UTC, Florian Schmaus
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Florian Schmaus gentoo-dev 2021-11-04 07:48:08 UTC
Created attachment 748428 [details]
build.log

$ emerge portage
…
Creating file build/_sources/portage.xml.metadata.rst.
Running Sphinx v4.2.0
copying lib/portage/tests/xpak/__test__.py -> /var/tmp/portage/sys-app
Extension error:
Could not import extension sphinx_epytext (exception: No module named 'sphinx_epytext')
make: *** [Makefile:32: html] Error 2
make: Leaving directory '/var/tmp/portage/sys-apps/portage-3.0.28/work/portage-3.0.28/doc/api'
Building API documentation...
Traceback (most recent call last):
  File "/var/tmp/portage/sys-apps/portage-3.0.28/work/portage-3.0.28/setup.py", line 806, in <module>
    setup(
  File "/usr/lib/python3.9/distutils/core.py", line 148, in setup
    dist.run_commands()
  File "/usr/lib/python3.9/distutils/dist.py", line 966, in run_commands
    self.run_command(cmd)
  File "/usr/lib/python3.9/distutils/dist.py", line 985, in run_command
    cmd_obj.run()
  File "/var/tmp/portage/sys-apps/portage-3.0.28/work/portage-3.0.28/setup.py", line 197, in run
    subprocess.check_call(["make", "-C", "doc/api", "html"], env=process_env)
  File "/usr/lib/python3.9/subprocess.py", line 373, in check_call
    raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['make', '-C', 'doc/api', 'html']' returned non-zero exit status 2.
 * ERROR: sys-apps/portage-3.0.28::gentoo failed (compile phase):
 *   (no error message)
 * 
 * Call stack:
 *     ebuild.sh, line  127:  Called src_compile
 *   environment, line 3683:  Called distutils-r1_src_compile
 *   environment, line 1425:  Called _distutils-r1_run_common_phase 'python_compile_all'
 *   environment, line  499:  Called multibuild_foreach_variant 'distutils-r1_run_phase' 'python_compile_all'
 *   environment, line 2694:  Called _multibuild_run 'distutils-r1_run_phase' 'python_compile_all'
 *   environment, line 2692:  Called distutils-r1_run_phase 'python_compile_all'
 *   environment, line 1413:  Called python_compile_all
 *   environment, line 3003:  Called esetup.py 'docbook' 'apidoc'
 *   environment, line 1891:  Called die
 * The specific snippet of code:
 *       "${@}" || die -n;
 * 
 * If you need support, post the output of `emerge --info '=sys-apps/portage-3.0.28::gentoo'`,
 * the complete build log and the output of `emerge -pqv '=sys-apps/portage-3.0.28::gentoo'`.
 * The complete build log is located at '/var/tmp/portage/sys-apps/portage-3.0.28/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/sys-apps/portage-3.0.28/temp/environment'.
 * Working directory: '/var/tmp/portage/sys-apps/portage-3.0.28/work/portage-3.0.28'
 * S: '/var/tmp/portage/sys-apps/portage-3.0.28/work/portage-3.0.28'
Comment 1 Florian Schmaus gentoo-dev 2021-11-04 07:48:46 UTC
Created attachment 748431 [details]
emerge --info
Comment 2 Florian Schmaus gentoo-dev 2021-11-04 07:49:14 UTC
Created attachment 748434 [details]
emerge -pqv portage
Comment 3 Zac Medico gentoo-dev 2021-11-04 21:35:19 UTC
This dependency from the sphinx-epytext ebuild is supposed to ensure that it is usable if an appropriate python interpreter is used:

RDEPEND=">=dev-python/sphinx-1.7.5[${PYTHON_USEDEP}]"

So, it looks like sphinx is using a python interpreter different from interpreter(s) that sphinx-epytext is installed for. We should be able to solve this by making the ebuild choose a more appropriate python interpreter. However, it seems simpler to make portage depend on dev-python/sphinx-epytext[${PYTHON_USEDEP}].
Comment 4 Larry the Git Cow gentoo-dev 2021-11-04 21:54:46 UTC
The bug has been closed via the following commit(s):

https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=29a1094f02ba289f4e225ff003f8165bea91d733

commit 29a1094f02ba289f4e225ff003f8165bea91d733
Author:     Zac Medico <zmedico@gentoo.org>
AuthorDate: 2021-11-04 21:47:15 +0000
Commit:     Zac Medico <zmedico@gentoo.org>
CommitDate: 2021-11-04 21:54:41 +0000

    sys-apps/portage: require sphinx-epytext[${PYTHON_USEDEP}]
    
    Closes: https://bugs.gentoo.org/821619
    Package-Manager: Portage-3.0.28, Repoman-3.0.3
    Signed-off-by: Zac Medico <zmedico@gentoo.org>

 sys-apps/portage/portage-3.0.28.ebuild | 4 ++--
 sys-apps/portage/portage-9999.ebuild   | 4 ++--
 2 files changed, 4 insertions(+), 4 deletions(-)

Additionally, it has been referenced in the following commit(s):

https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=0f094d7ba3c1fe921c661c253bf56ccc96e1bd6f

commit 0f094d7ba3c1fe921c661c253bf56ccc96e1bd6f
Author:     Zac Medico <zmedico@gentoo.org>
AuthorDate: 2021-11-04 21:44:37 +0000
Commit:     Zac Medico <zmedico@gentoo.org>
CommitDate: 2021-11-04 21:54:40 +0000

    dev-python/sphinx-epytext: PYTHON_COMPAT+=(pypy3)
    
    Bug: https://bugs.gentoo.org/821619
    Package-Manager: Portage-3.0.28, Repoman-3.0.3
    Signed-off-by: Zac Medico <zmedico@gentoo.org>

 dev-python/sphinx-epytext/sphinx-epytext-0.0.4.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)