This is a fresh gentoo install - no upgrade. Something is wrong with the libxmlb library. It does not install and this is what one gets: teoria01 /home/gfaccin # emerge zenity -uva These are the packages that would be merged, in order: Calculating dependencies... done! Dependency resolution took 1.12 s (backtrack: 0/20). [ebuild N ] dev-libs/libxmlb-0.3.19:0/2::gentoo USE="introspection lzma zstd -doc -stemmer -test" 0 KiB [ebuild N ] dev-libs/appstream-1.0.3:0/5::gentoo USE="introspection qt6 -apt -doc -systemd -test" 0 KiB [ebuild N ] gui-libs/libadwaita-1.5.2:1::gentoo USE="introspection vala -test" 0 KiB [ebuild N ] gnome-extra/zenity-4.0.1::gentoo USE="-man -webkit" 0 KiB Total: 4 packages (4 new), Size of downloads: 0 KiB Would you like to merge these packages? [Yes/No] yes >>> Verifying ebuild manifests >>> Emerging (1 of 4) dev-libs/libxmlb-0.3.19::gentoo * Fetching files in the background. * To view fetch progress, run in another terminal: * tail -f /var/log/emerge-fetch.log * libxmlb-0.3.19.tar.gz BLAKE2B SHA512 size ;-) ... [ ok ] * Relative path found in PYTHONPATH: * * PYTHONPATH='/home/gfaccin/.local/lib64/:' * * This is guaranteed to cause random breakage. Please make sure that * your PYTHONPATH contains absolute paths only (and only if necessary). * Note that empty values (including ':' at either end and an empty * PYTHONPATH) count as the current directory. If no PYTHONPATH * is intended, it needs to be unset instead. * ERROR: dev-libs/libxmlb-0.3.19::gentoo failed (setup phase): * Relative paths in PYTHONPATH are forbidden: $' * ' * * Call stack: * ebuild.sh, line 136: Called pkg_setup * libxmlb-0.3.19.ebuild, line 53: Called python-any-r1_pkg_setup * python-any-r1.eclass, line 343: Called python_setup * python-any-r1.eclass, line 275: Called _python_sanity_checks * python-utils-r1.eclass, line 1595: Called die * The specific snippet of code: * die "Relative paths in PYTHONPATH are forbidden: ${x@Q}" * * If you need support, post the output of `emerge --info '=dev-libs/libxmlb-0.3.19::gentoo'`, * the complete build log and the output of `emerge -pqv '=dev-libs/libxmlb-0.3.19::gentoo'`. * The complete build log is located at '/var/tmp/portage/dev-libs/libxmlb-0.3.19/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/dev-libs/libxmlb-0.3.19/temp/die.env'. * Working directory: '/var/tmp/portage/dev-libs/libxmlb-0.3.19/empty' * S: '/var/tmp/portage/dev-libs/libxmlb-0.3.19/work/libxmlb-0.3.19' >>> Failed to emerge dev-libs/libxmlb-0.3.19, Log file: >>> '/var/tmp/portage/dev-libs/libxmlb-0.3.19/temp/build.log'
``` * * This is guaranteed to cause random breakage. Please make sure that * your PYTHONPATH contains absolute paths only (and only if necessary). * Note that empty values (including ':' at either end and an empty * PYTHONPATH) count as the current directory. If no PYTHONPATH * is intended, it needs to be unset instead. ``` seems to explain it; your environment is contaminated. Please emerge with a clean environment.
Sorry friend, but this is too cryptic for a common user. I've just finished an install from the handbook. No customization, no nothing - just followed it through. If this means a tainted environment, then at least some clarification is needed in the install handbook.
(In reply to Giovani M. Faccin from comment #2) > Sorry friend, but this is too cryptic for a common user. > > I've just finished an install from the handbook. No customization, no > nothing - just followed it through. If this means a tainted environment, > then at least some clarification is needed in the install handbook. You have an environment variable called 'PYTHONPATH' set. It probably leaked in from whatever your installation environment is. Depending on how you chroot in, that environment variable may be cleared. Not a bug, please consult one of our support channels.
Let's see if the docs are right. They're at https://wiki.gentoo.org/wiki/Handbook:AMD64/Installation/Base#Entering_the_new_environment. It looks like chroot /bin/bash should do the right thing?
(In reply to Giovani M. Faccin from comment #2) > Sorry friend, but this is too cryptic for a common user. > > I've just finished an install from the handbook. No customization, no > nothing - just followed it through. If this means a tainted environment, > then at least some clarification is needed in the install handbook. Could I ask what install media (Gentoo installcd, Linux Mint, etc) that you are using to install from please? If you have the commands in your bash history as well it would be most helpful in getting to the bottom of this one.
I've installed from a Gentoo flash drive. And indeed, this problem is now coming up for other packages as well. :o| I have no clue on how to fix PYTHONPATH issue. I've reinstalled python using portage and it went ok, but the issue still persists. Gentoolkit is not installing because of the same error. There goes the weekend... :( We can close the bug. Indeed it's not specific for this library. My bad.
How did you end up with this exported: PYTHONPATH='/home/gfaccin/.local/lib64/: In general, you should *never* have PYTHONPATH exported as root. Additionally, this specifies a non-root homedir, which should always be cleared when becoming root. Thirdly, that is a fairly odd directory to have python modules in.' The implication here is that whatever environment you used to perform the handbook install steps had some correctness issues which should probably be fixed, and that leaked into your gentoo chroot environment as well.
Found it! Thank you for pointing it out. The cause was this: I've copied the .bashrc file from another computer in my user account (not the root one). That has a ton of configurations and customizations. Inside those, for some arcane reason, was that line. It was not applied to the root account, but to the user account. But it caused all those effects. Removing it and rebooting appears to have solved it. Handbook is ok! Cheers!
