Created attachment 598348 [details] sys conf steps to reproduce: * following guide as per https://wiki.gentoo.org/wiki/Handbook:AMD64 till reaching https://wiki.gentoo.org/wiki/Handbook:AMD64/Installation/Base#Updating_the_.40world_set ___ having reached that point the building process then comes to end with emerge -uavDN --verbose-conflicts @world * IMPORTANT: 6 news items need reading for repository 'gentoo'. * Use eselect news read to view new items. These are the packages that would be merged, in order: Calculating dependencies ... done! !!! Multiple package instances within a single package slot have been pulled !!! into the dependency graph, resulting in a slot conflict: dev-lang/perl:0 (dev-lang/perl-5.30.1:0/5.30::gentoo, ebuild scheduled for merge) pulled in by (no parents that aren't satisfied by other packages in this slot) (dev-lang/perl-5.28.2-r1:0/5.28::gentoo, installed) pulled in by dev-lang/perl:0/5.28= required by (dev-perl/Locale-gettext-1.70.0:0/0::gentoo, installed) ^^^^^^^^ dev-lang/perl:0/5.28=[-build(-)] required by (dev-perl/XML-Parser-2.440.0:0/0::gentoo, installed) ^^^^^^^^ sys-libs/readline:0 (sys-libs/readline-8.0_p1-r1:0/8::gentoo, ebuild scheduled for merge) pulled in by >=sys-libs/readline-8.0:0= required by (app-shells/bash-5.0_p11:0/0::gentoo, ebuild scheduled for merge) ^^ ^^^^^^ (sys-libs/readline-7.0_p5-r1:0/7::gentoo, installed) pulled in by sys-libs/readline:0/7= required by (app-crypt/gnupg-2.2.17:0/0::gentoo, installed) ^^^^^ dev-python/numpy:0 (dev-python/numpy-1.17.4:0/0::gentoo, ebuild scheduled for merge) pulled in by (no parents that aren't satisfied by other packages in this slot) (dev-python/numpy-1.16.5:0/0::gentoo, ebuild scheduled for merge) pulled in by dev-python/numpy[python_targets_python2_7(-)?,-python_single_target_python2_7(-),python_targets_python3_5(-)?,-python_single_target_python3_5(-),python_targets_python3_6(-)?,-python_single_target_python3_6(-),python_targets_python3_7(-)?,-python_single_target_python3_7(-)] required by (dev-python/future-0.18.2:0/0::gentoo, ebuild scheduled for merge) It may be possible to solve this problem by using package.mask to prevent one of those packages from being selected. However, it is also possible that conflicting dependencies exist such that they are impossible to satisfy simultaneously. If such a conflict exists in the dependencies of two different packages, then those packages can not be installed simultaneously. For more information, see MASKED PACKAGES section in the emerge man page or refer to the Gentoo Handbook. The following USE changes are necessary to proceed: (see "package.use" in the portage(5) man page for more details) # required by dev-util/cmake-3.16.0::gentoo[test] # required by app-text/poppler-0.82.0::gentoo # required by app-text/texlive-core-2019-r4::gentoo # required by dev-texlive/texlive-fontsrecommended-2019::gentoo # required by app-text/dvipng-1.15-r1::gentoo[test] # required by dev-python/sphinx-1.7.5-r1::gentoo[test,-latex] # required by dev-python/pbr-5.1.1::gentoo[test] # required by dev-python/traceback2-1.4.0::gentoo # required by dev-python/unittest2-1.1.0::gentoo # required by dev-python/contextlib2-0.6.0::gentoo[test,python_targets_python3_6,python_targets_python2_7,-python_targets_python3_7,-python_targets_pypy,-python_targets_pypy3,-python_targets_python3_5] # required by dev-python/importlib_metadata-1.1.0::gentoo[test,python_targets_python2_7,-python_targets_pypy] # required by dev-python/pluggy-0.13.1::gentoo[python_targets_python2_7,-python_targets_python3_5,test,-python_targets_python3_7,-python_targets_pypy,python_targets_python3_6,-python_targets_pypy3] # required by dev-python/pytest-4.6.6::gentoo[test] # required by dev-python/py-1.8.0::gentoo[test] >=x11-base/xorg-server-1.20.6 xvfb # required by dev-python/hypothesis-4.50.6::gentoo[python_targets_python2_7] # required by dev-python/chardet-3.0.4::gentoo[test] # required by dev-python/requests-2.22.0::gentoo[test] # required by dev-python/sphinx-1.7.5-r1::gentoo # required by dev-python/pbr-5.1.1::gentoo[test] # required by dev-python/traceback2-1.4.0::gentoo # required by dev-python/unittest2-1.1.0::gentoo # required by dev-python/contextlib2-0.6.0::gentoo[test,python_targets_python3_6,python_targets_python2_7,-python_targets_python3_7,-python_targets_pypy,-python_targets_pypy3,-python_targets_python3_5] # required by dev-python/importlib_metadata-1.1.0::gentoo[test,python_targets_python2_7,-python_targets_pypy] # required by dev-python/pluggy-0.13.1::gentoo[python_targets_python2_7,-python_targets_python3_5,test,-python_targets_python3_7,-python_targets_pypy,python_targets_python3_6,-python_targets_pypy3] # required by dev-python/pytest-4.6.6::gentoo[test] # required by dev-python/py-1.8.0::gentoo[test] >=dev-lang/python-2.7.17:2.7 sqlite # required by dev-python/hypothesis-4.50.6::gentoo[python_targets_python3_6] # required by dev-python/chardet-3.0.4::gentoo[test] # required by dev-python/requests-2.22.0::gentoo[test] # required by dev-python/sphinx-1.7.5-r1::gentoo # required by dev-python/pbr-5.1.1::gentoo[test] # required by dev-python/traceback2-1.4.0::gentoo # required by dev-python/unittest2-1.1.0::gentoo # required by dev-python/contextlib2-0.6.0::gentoo[test,python_targets_python3_6,python_targets_python2_7,-python_targets_python3_7,-python_targets_pypy,-python_targets_pypy3,-python_targets_python3_5] # required by dev-python/importlib_metadata-1.1.0::gentoo[test,python_targets_python2_7,-python_targets_pypy] # required by dev-python/pluggy-0.13.1::gentoo[python_targets_python2_7,-python_targets_python3_5,test,-python_targets_python3_7,-python_targets_pypy,python_targets_python3_6,-python_targets_pypy3] # required by dev-python/pytest-4.6.6::gentoo[test] # required by dev-python/py-1.8.0::gentoo[test] >=dev-lang/python-3.6.9:3.6 sqlite # required by dev-python/pycurl-7.43.0.3::gentoo[test] # required by www-servers/tornado-5.1::gentoo[test] # required by dev-python/urllib3-1.25.7::gentoo[test] # required by dev-python/requests-2.22.0::gentoo[test] # required by dev-python/sphinx-1.7.5-r1::gentoo # required by dev-python/pbr-5.1.1::gentoo[test] # required by dev-python/traceback2-1.4.0::gentoo # required by dev-python/unittest2-1.1.0::gentoo # required by dev-python/contextlib2-0.6.0::gentoo[test,python_targets_python3_6,python_targets_python2_7,-python_targets_python3_7,-python_targets_pypy,-python_targets_pypy3,-python_targets_python3_5] # required by dev-python/importlib_metadata-1.1.0::gentoo[test,python_targets_python2_7,-python_targets_pypy] # required by dev-python/pluggy-0.13.1::gentoo[python_targets_python2_7,-python_targets_python3_5,test,-python_targets_python3_7,-python_targets_pypy,python_targets_python3_6,-python_targets_pypy3] # required by dev-python/pytest-4.6.6::gentoo[test] # required by dev-python/py-1.8.0::gentoo[test] >=net-misc/curl-7.67.0-r1 http2 # required by app-shells/fish-3.0.2::gentoo # required by dev-python/argcomplete-1.10.3::gentoo[test] # required by dev-python/pytest-4.6.6::gentoo[test] # required by dev-python/sphinx-1.7.5-r1::gentoo[test] # required by dev-python/pbr-5.1.1::gentoo[test] # required by dev-python/traceback2-1.4.0::gentoo # required by dev-python/unittest2-1.1.0::gentoo # required by dev-python/contextlib2-0.6.0::gentoo[test,python_targets_python3_6,python_targets_python2_7,-python_targets_python3_7,-python_targets_pypy,-python_targets_pypy3,-python_targets_python3_5] # required by dev-python/importlib_metadata-1.1.0::gentoo[test,python_targets_python2_7,-python_targets_pypy] # required by dev-python/pluggy-0.13.1::gentoo[python_targets_python2_7,-python_targets_python3_5,test,-python_targets_python3_7,-python_targets_pypy,python_targets_python3_6,-python_targets_pypy3] >=dev-libs/libpcre2-10.34 pcre32 # required by app-text/dvipng-1.15-r1::gentoo # required by dev-python/sphinx-1.7.5-r1::gentoo[test,-latex] # required by dev-python/pbr-5.1.1::gentoo[test] # required by dev-python/traceback2-1.4.0::gentoo # required by dev-python/unittest2-1.1.0::gentoo # required by dev-python/contextlib2-0.6.0::gentoo[test,python_targets_python3_6,python_targets_python2_7,-python_targets_python3_7,-python_targets_pypy,-python_targets_pypy3,-python_targets_python3_5] # required by dev-python/importlib_metadata-1.1.0::gentoo[test,python_targets_python2_7,-python_targets_pypy] # required by dev-python/pluggy-0.13.1::gentoo[python_targets_python2_7,-python_targets_python3_5,test,-python_targets_python3_7,-python_targets_pypy,python_targets_python3_6,-python_targets_pypy3] # required by dev-python/pytest-4.6.6::gentoo[test] # required by dev-python/py-1.8.0::gentoo[test] >=media-libs/gd-2.2.5-r2 jpeg png Would you like to add these changes to your config files? [Yes/No] y Autounmask changes successfully written. * IMPORTANT: config file '/etc/portage/package.use/zz-autounmask' needs updating. * See the CONFIGURATION FILES and CONFIGURATION FILES UPDATE TOOLS * sections of the emerge man page to learn how to update config files. !!! The ebuild selected to satisfy "media-libs/tiff:0" has unmet requirements. - media-libs/tiff-4.1.0::gentoo USE="cxx test zlib -jbig -jpeg -lzma -static-libs -webp -zstd" ABI_X86="(64) -32 (-x32)" The following REQUIRED_USE flag constraints are unsatisfied: test? ( jpeg ) (dependency required by "media-libs/openjpeg-2.3.1::gentoo" [ebuild]) (dependency required by "app-text/poppler-0.82.0::gentoo[jpeg2k]" [ebuild]) (dependency required by "app-text/texlive-core-2019-r4::gentoo" [ebuild]) (dependency required by "dev-texlive/texlive-fontsrecommended-2019::gentoo" [ebuild]) (dependency required by "app-text/dvipng-1.15-r1::gentoo[test]" [ebuild]) (dependency required by "dev-python/sphinx-1.7.5-r1::gentoo[test,-latex]" [ebuild]) (dependency required by "dev-python/pbr-5.1.1::gentoo[test]" [ebuild]) (dependency required by "dev-python/traceback2-1.4.0::gentoo" [ebuild]) (dependency required by "dev-python/unittest2-1.1.0::gentoo" [ebuild]) (dependency required by "dev-python/contextlib2-0.6.0::gentoo[test,python_targets_python3_6,python_targets_python2_7,-python_targets_python3_7,-python_targets_pypy,-python_targets_pypy3,-python_targets_python3_5]" [ebuild]) (dependency required by "dev-python/importlib_metadata-1.1.0::gentoo[test,python_targets_python2_7,-python_targets_pypy]" [ebuild]) (dependency required by "dev-python/pluggy-0.13.1::gentoo[python_targets_python2_7,-python_targets_python3_5,test,-python_targets_python3_7,-python_targets_pypy,python_targets_python3_6,-python_targets_pypy3]" [ebuild]) (dependency required by "dev-python/pytest-4.6.6::gentoo[test]" [ebuild]) (dependency required by "dev-python/py-1.8.0::gentoo[test]" [ebuild])
You need to fix this: * IMPORTANT: config file '/etc/portage/package.use/zz-autounmask' needs updating. * See the CONFIGURATION FILES and CONFIGURATION FILES UPDATE TOOLS And this: !!! The ebuild selected to satisfy "media-libs/tiff:0" has unmet requirements. - media-libs/tiff-4.1.0::gentoo USE="cxx test zlib -jbig -jpeg -lzma -static-libs -webp -zstd" ABI_X86="(64) -32 (-x32)" The following REQUIRED_USE flag constraints are unsatisfied: test? ( jpeg ) This isn't a bug, please see our support venues (forums, IRC, gentoo-users mailing list) if you need help with these things.
The issue not present with the stable branch. Pointing to support venues is not going to resolve the matter, which clearly is a bug since emerge should not pull multiple package instances with different versions into the dependency graph to begin with. Apprently there are package dependency conflicts. The misisng required USE flag is produced by the Gentoo code and not caused by settings the user introduced. Well, if you cannot be bothered to consider this being bug then perhaps wait until other users being hit by it and maybe that will change the perspective.
The slot conflicts will most likely resolve themselves when you have resolved the other real issues. Please try. "The misisng required USE flag is produced by the Gentoo code and not caused by settings the user introduced." You have set FEATURES=test (which enables USE=test), and that's what set off the REQUIRED_USE problem. You are installing desktop apps w/o using a desktop profile (and the nice USE flags it sets) and that is most likely causing the other "problem".
As far as trying goes: * same config in stable branch does not produce the issue(s) * some time back (probably 4 - 5 weeks) also with the experimental branch the issue(s) not been present ___ I dot not see what is wrong with FEATURES=test > Runs package-specific test cases to verify that everything was built properly. which works with no issue in the stable branch. ___ It is unclear why desktop app should be installed since I did not specify any and using this profile [18] default/linux/amd64/17.1/hardened (stable) * Any installation of desktops apps then must be initiated/automated by some Gentoo script. the make.conf leveraged reads: COMMON_FLAGS="-march=native -O2 -pipe -maccumulate-outgoing-args -malign-data=abi -mtls-dialect=gnu2" ACCEPT_KEYWORDS="~amd64" PORTAGE_IONICE_COMMAND="ionice -c 3 -p \${PID}" PORTAGE_NICENESS="19" MAKEOPTS="-j9" AUTOCLEAN="yes" L10N="en-US" LANG="en_US.UTF-8" EMERGE_DEFAULT_OPTS="-va" FEATURES="candy fail-clean ipc-sandbox multilib-strict network-sandbox parallel-fetch parallel-install sandbox sfperms stricter suidctl test unmerge-orphans userfetch xattr" CFLAGS="${COMMON_FLAGS}" CXXFLAGS="${COMMON_FLAGS}" FCFLAGS="${COMMON_FLAGS}" FFLAGS="${COMMON_FLAGS}" # NOTE: This stage was built with the bindist Use flag enabled PORTDIR="/var/db/repos/gentoo" DISTDIR="/var/cache/distfiles" PKGDIR="/var/cache/binpkgs" # This sets the language of build output to English. # Please keep this setting intact when reporting bugs. LC_MESSAGES=C
If you set FEATURES=test, you may need to enable more USE flags. That's all that's going on here. There's no bug. It doesn't matter if it worked on stable.
The main issue/cause of the reported bug is that emerge is pulling multiple package instances with different versions into the dependency graph. That indicates dependcy conflicts. Which does not happen in the stable branch - with the very same sys conf. And yet it is not a bug... And since FEATURES=test works without that issue in the stable branch sans any whatsoever additional flag it would indicate being a bug in the experimental branch. Anyway, it is apparent that there is no interest to look into it and thus it seems fruitless to dwell on it further. Whilst I thought initally highly of Gentoo this sort of response to bug reports is rather detrimental, will just hop to another repo.
Please seek our support venues, you have some common new-user issues to tackle. I am very active in #gentoo (IRC) and would be happy to assist you there. But there is not a *BUG* to be handled in our bug tracker here. There are USE flag issues to tackle, if you tackle those then there *WILL BE NO MORE SLOT CONFLICTS*. I'm sorry if I am coming off roughly, I'm just trying to be direct. We can help you in #gentoo, or on the forums, or on the user ML. There is no bug. When emerge asks you to add a new USE flag, that's not a bug.
Created attachment 598396 [details] revised sys conf No issue with being direct but dismissing this as user ignorance is. If test requires certain USE flags then it would be expected that the Gentoo code takes care of it, like it does in the stable branch where the issue does not exhibit. Even with the missing USE flags (jpeg cairo corefonts truetype) added the matter is not resolved but printing * Error: circular dependencies: (dev-python/attrs-19.3.0:0/0::gentoo, ebuild scheduled for merge) depends on (dev-python/pytest-4.6.6:0/0::gentoo, ebuild scheduled for merge) (buildtime) (dev-python/attrs-19.3.0:0/0::gentoo, ebuild scheduled for merge) (buildtime) It might be possible to break this cycle by applying any of the following changes: - dev-python/pytest-4.6.6 (Change USE: -test) - dev-python/attrs-19.3.0 (Change USE: -test) Which is basically telling to remove test in order to be able to proceed. Having removed test the installation then proceeds.
> > If test requires certain USE flags then it would be expected that the Gentoo > code takes care of it, like it does in the stable branch where the issue > does not exhibit. > It might be expected by you, but it's not expected in general. Stable doesn't have any magic to autoresolve this, any USE requirement today in unstable will probably hit unstable soon. None of this is a "bug", still. You probably shouldn't be enabling tests globally, as a new user. Or if you do, wait until you have all your packages installed the first time already, then rebuild them with tests on. This will probably alleviate some of the dependency woes. I'm sorry to dismiss this as "user ignorance", I would state it more nicely like "new user inexperience", but it's the same thing really. If you really disagree with me entirely, would you be willing to open a new bug report with the information you have now, and let someone else work on it? I won't touch it, you can get a fresh set of eyes and hands on it.
