These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild N ] dev-python/configparser-3.5.0-r1::gentoo PYTHON_TARGETS="python2_7 -pypy" 0 KiB [ebuild U ] app-admin/webapp-config-1.55::gentoo [1.54-r2::gentoo] USE="portage" PYTHON_TARGETS="python2_7 python3_4 -pypy -python3_5 -python3_6" 71 KiB [blocks B ] dev-python/configparser ("dev-python/configparser" is blocking app-admin/webapp-config-1.55) Total: 2 packages (1 upgrade, 1 new), Size of downloads: 71 KiB Conflict: 1 block (1 unsatisfied) * Error: The above package list contains packages which cannot be * installed at the same time on the same system. (dev-python/configparser-3.5.0-r1:0/0::gentoo, ebuild scheduled for merge) pulled in by >=dev-python/configparser-3.5.0[python_targets_python2_7(-)?,-python_single_target_python2_7(-)] (>=dev-python/configparser-3.5.0[python_targets_python2_7(-),-python_single_target_python2_7(-)]) required by (dev-python/entrypoints-0.2.2:0/0::gentoo, installed) (app-admin/webapp-config-1.55:0/0::gentoo, ebuild scheduled for merge) pulled in by >=app-admin/webapp-config-1.50.15 required by (dev-db/phpmyadmin-4.7.1:4.7.1/4.7.1::gentoo, installed) Reproducible: Always
Same here. in webapp-config-1.55.ebuild I found DEPEND="... !dev-python/configparser ..." Could some one explain why?
(In reply to Alex from comment #1) > Same here. > > in webapp-config-1.55.ebuild I found > > DEPEND="... > !dev-python/configparser > ..." > > Could some one explain why? Same goes for webapp-config-9999.ebuild .... Insane.....
Here’s a “mee too”. Only webapp-config-1.54-r2 does not contain !configparser, which is the version I had installed until now. For (probably a sound reason) 1.54-r2 became keyworded, so another version gets selected by portage.
For an explanation as to why webapp-config blocks the configparser package, please see bug #528752, it will explain exactly why this happened. I can attempt to resolve this inside the code without the need to block it but if I recall correctly this was a choice made due to the fact that we'd have to modify the configuration files completely if we didn't block it.
In retrospect, I have made a change to the code awhile back which removes the need to have this blocker in ebuilds. I have just confirmed this myself as well, so I will be removing it from the 9999 and 1.55 ebuilds, respectively.
I've made changes to the ebuild, feel free to re-install.