[gentoo-user] app-portage/repoman-3.0.3-r2 slot conflict

[Dale]

Howdy,

I been getting a error message about repoman not being in good shape for
a while.  I thought maybe it was something that would be fixed soon
enough or it would spit out a error that makes sense to me.  Well, been
a few weeks and it is still complaining about it.  I tried to update
repoman itself so that it would give the most information.  It doesn't
say much when doing my usual world update except that it is skipping it.
This is the most informative error I can get it to give me. 


root@fireball / # emerge -a =app-portage/repoman-3.0.3-r2

These are the packages that would be merged, in order:

Calculating dependencies... done!
[ebuild     UD~] sys-apps/portage-3.0.30-r5::gentoo [3.0.34::gentoo]
USE="(ipc) native-extensions rsync-verify -apidoc -build -doc
-gentoo-dev (-selinux) -test -xattr" PYTHON_TARGETS="python3_10 -pypy3
-python3_8 -python3_9 -python3_11" 1,131 KiB
[ebuild     U  ] app-portage/repoman-3.0.3-r2::gentoo [3.0.3-r1::gentoo]
PYTHON_TARGETS="python3_10 (-pypy3) -python3_8 -python3_9" 0 KiB

Total: 2 packages (1 upgrade, 1 downgrade), Size of downloads: 1,131 KiB

!!! Multiple package instances within a single package slot have been pulled
!!! into the dependency graph, resulting in a slot conflict:

sys-apps/portage:0

  (sys-apps/portage-3.0.30-r5:0/0::gentoo, ebuild scheduled for merge)
USE="(ipc) native-extensions rsync-verify -apidoc -build -doc
-gentoo-dev (-selinux) -test -xattr" ABI_X86="(64)"
PYTHON_TARGETS="python3_10 -pypy3 -python3_11 -python3_8 -python3_9"
pulled in by
   
<sys-apps/portage-3.0.31[python_targets_pypy3(-)?,python_targets_python3_8(-)?,python_targets_python3_9(-)?,python_targets_python3_10(-)?]
required by (app-portage/repoman-3.0.3-r2:0/0::gentoo, ebuild scheduled
for merge) USE="" ABI_X86="(64)" PYTHON_TARGETS="python3_10 (-pypy3)
-python3_8 -python3_9"
    ^                
^^^^^^                                                                                                                                                                                                                                                                                                                                                                                                                                           


  (sys-apps/portage-3.0.34:0/0::gentoo, installed) USE="(ipc)
native-extensions rsync-verify -apidoc -build -doc -gentoo-dev
(-selinux) -test -xattr" ABI_X86="(64)" PYTHON_TARGETS="python3_10
-pypy3 -python3_11 -python3_8 -python3_9" pulled in by
   
>=sys-apps/portage-3.0.32[python_targets_pypy3(-)?,python_targets_python3_8(-)?,python_targets_python3_9(-)?,python_targets_python3_10(-)?,python_targets_python3_11(-)?]
required by (app-portage/gentoolkit-0.6.1-r3:0/0::gentoo, installed)
USE="-test" ABI_X86="(64)" PYTHON_TARGETS="python3_10 -pypy3 -python3_11
-python3_8 -python3_9"


And some more info:


root@fireball / # equery list -po portage repoman
 * Searching for portage ...
[-P-] [  ] sys-apps/portage-3.0.30-r3:0
[-P-] [  ] sys-apps/portage-3.0.30-r5:0
[-P-] [  ] sys-apps/portage-3.0.32:0
[-P-] [  ] sys-apps/portage-3.0.33:0
[IP-] [  ] sys-apps/portage-3.0.34:0
[-P-] [M-] sys-apps/portage-9999:0

 * Searching for repoman ...
[I--] [??] app-portage/repoman-3.0.3-r1:0
[-P-] [  ] app-portage/repoman-3.0.3-r2:0
root@fireball / #


I did keyword all but the 9999 version.  I like the new stuff but not
the untested stuff.  It looks like the version of repoman I have
installed is not even in the tree anymore too.  It looks like it could
be a USE flag problem above but I'm not sure about that either.  Here is
some info on that. 


root@fireball / # grep -r python /etc/portage/
/etc/portage/package.accept_keywords/package.keywords:dev-python/PyQt-builder
/etc/portage/package.accept_keywords/package.keywords:dev-python/PyQtWebEngine
/etc/portage/package.accept_keywords/package.keywords:dev-python/python-slip
/etc/portage/package.accept_keywords/package.keywords:=dev-python/cchardet-2.1.7
/etc/portage/package.accept_keywords/package.keywords:dev-python/PyQt5-sip
/etc/portage/package.accept_keywords/package.keywords:dev-python/sip
/etc/portage/package.accept_keywords/package.keywords:dev-python/PyQt5
/etc/portage/package.accept_keywords/package.keywords:dev-python/wxpython
/etc/portage/package.use/package.use:=sci-electronics/klayout-0.27.3
python_single_target_python3_9
/etc/portage/package.use/package.use:app-accessibility/speech-dispatcher
python
/etc/portage/package.use/package.use:dev-python/PyQt5 webchannel
/etc/portage/package.use/package.use:>=dev-libs/boost-1.47.0-r1:0 python
/etc/portage/package.use/package.use:>=mate-base/mate-menus-1.18.0 python
/etc/portage/package.use/package.use:media-libs/mlt python frei0r qt5
/etc/portage/package.use/package.use:media-gfx/gimp doc python png jpeg
exif lcms
root@fireball / #


I try to let the devs manage the python stuff.  It can get tricky, and
messy, if one starts messing with it. 

I can't figure this thing out.  Anyone see what is causing this
problem?  I'd like to get this fixed if I can or if it is a bug, report
it so it can get fixed.  Odds are, I did something somewhere.  lol 

Thanks!

Dale

:-)  :-)