On Sun, 14 Feb 2021 10:56:03 +0000
Neil Bothwick <n...@digimed.co.uk> wrote:
> ~java-config-2.2.0 isn't in the portage tree, the only version is
> 2.3.1.
>
> > [installed]) (dependency required by
> > "sys-devel/gettext-0.20.2::gentoo"
>
> Also not in the tree.
>
> I'd start by unmerging these two, quickpkg them first, and running a
> deep world update.
# emerge --unmerge ~java-config-2.2.0
* This action can remove important packages! In order to be safer, use
* `emerge -pv --depclean <atom>` to check for reverse dependencies before
* removing packages.
dev-java/java-config
selected: 2.2.0-r4
<snip>
# emerge --unmerge ~sys-devel/gettext-0.20.2
* This action can remove important packages! In order to be safer, use
* `emerge -pv --depclean <atom>` to check for reverse dependencies before
* removing packages.
sys-devel/gettext
selected: 0.20.2
<snip>
OK, that seemed to work: picked a single version each time.
Checking java-config it's at 2.3.1 in the repository, trying
"emerge --pretend java-config" failes with a long list of conflicts,
most of which appear to include python versions.
Ditto sys-devel/gettext.
Attempting the world-merge:
# /usr/bin/emerge --deep --with-bdeps y --complete-graph y \
--autounmask-write --verbose-conflicts --jobs --load-average 4 \
--keep-going --update @world 2>&1 |
tee /tmp/b ;
* IMPORTANT: config file '/etc/portage/package.use/zz_autoconfigure' needs
updating.
# git diff zz_autoconfigure ._cfg0000_zz_autoconfigure
diff --git a/zz_autoconfigure b/._cfg0000_zz_autoconfigure
index 22069a3..86e9b33 100644
--- a/zz_autoconfigure
+++ b/._cfg0000_zz_autoconfigure
@@ -272,3 +272,7 @@ media-libs/gegl cairo
# required by @selected
# required by @world (argument)
>=app-crypt/pinentry-1.1.1 gnome-keyring
+# required by media-video/cheese-3.34.0-r1::gentoo
+# required by @selected
+# required by @world (argument)
+>=media-libs/gst-plugins-base-1.16.3 theora
# mv ._cfg0000_zz_autoconfigure diff zz_autoconfigure;
Second pass:
# /usr/bin/emerge --deep --with-bdeps y --complete-graph y \
--autounmask-write --verbose-conflicts --jobs --load-average 4 \
--keep-going --update @world 2>&1 |
tee /tmp/b ;
!!! Multiple package instances within a single package slot have been pulled
!!! into the dependency graph, resulting in a slot conflict:
dev-python/idna:0
(dev-python/idna-3.1:0/0::gentoo, ebuild scheduled for merge) USE=""
ABI_X86="(64)" PYTHON_TARGETS="python3_8 -pypy3 -python3_7 -python3_9" pulled
in by
(no parents that aren't satisfied by other packages in this slot)
(dev-python/idna-2.10-r1:0/0::gentoo, ebuild scheduled for merge) USE=""
ABI_X86="(64)" PYTHON_TARGETS="python3_8 -pypy3 -python3_7 -python3_9" pulled
in by
<dev-python/idna-3[python_targets_pypy3(-)?,python_targets_python3_7(-)?,python_targets_python3_8(-)?,python_targets_python3_9(-)?,-python_single_target_pypy3(-),-python_single_target_python3_7(-),-python_single_target_python3_8(-),-python_single_target_python3_9(-)]
required by (dev-python/requests-2.25.1-r1:0/0::gentoo, ebuild scheduled for
merge) USE="-socks5 -test" ABI_X86="(64)" PYTHON_TARGETS="python3_8 -pypy3
-python3_7 -python3_9"
<snip>
Full output at:
<https://pastebin.com/qhyhW0mx>
At this point the various targets I've tried are all commented out
(whitespace added):
# grep PYTHON /etc/portage/make.conf /etc/portage/package.use/steamer ;
/etc/portage/make.conf:...
#PYTHON_TARGETS="python3_6 python3_7 python3_8 python3_9"
#PYTHON_SINGLE_TARGET="python3_9"
/etc/portage/package.use/steamer:..
#*/* PYTHON_TARGETS="-python2_7 python3_6 python3_6"
#*/* PYTHON_SINGLE_TARGET="python3_7"
Q: Is there any combination of targets that would suffice to get
things cleaned up to the point where I could eventuall remove
them?
I've tried this with an initially empty local & zz_autoconfig just
moving the generated autoconfig's in place as they are generated
but that didn't work either.
After zeroing zz_autoconfig and running a few emerges I get a autoconfig
file that hits a brick wall.
Thank you
--
Steven Lembark
Workhorse Computing
lemb...@wrkhors.com
+1 888 359 3508
