Apparently up to 3005-r1: NonsolvableDepsInStable: version 3005-r1: nonsolvable depset(rdepend) keyword(~amd64) stable profile (default/linux/amd64/17.1) (52 total): solutions: [ <dev-python/importlib_metadata-5[python_targets_python3_10(-),python_targets_python3_8(-),python_targets_python3_9(-)] ]
3005.1 and after do not depend on dev-python/importlib_metadata as of today, not sure why: # grep -l dev-python/importlib_metadata *.ebuild salt-3004.2-r2.ebuild salt-3005-r1.ebuild # grep -vl dev-python/importlib_metadata *.ebuild salt-3004.2-r2.ebuild salt-3005.1.ebuild salt-3005.1-r1.ebuild salt-3005-r1.ebuild @chutzpah do you remember why you dropped the dev-python/importlib_metadata dependency when adding 3005.1? @mgorny this is fixed for testing but not for stable. How should we proceed?
(In reply to Sebastian Pipping from comment #1) > # grep -vl dev-python/importlib_metadata *.ebuild > salt-3004.2-r2.ebuild > salt-3005.1.ebuild > salt-3005.1-r1.ebuild > salt-3005-r1.ebuild PS: That^^ logic was broken, second try: # ls -1 *.ebuild \ | grep -v -f <(grep -l dev-python/importlib_metadata *.ebuild) salt-3005.1.ebuild salt-3005.1-r1.ebuild
Could it be this is fixed already? Status quo today: # git --no-pager grep importlib . files/salt-3005.1-importlib-metadata-5-r1.patch: entry_points = importlib_metadata.entry_points() files/salt-3005.1-importlib-metadata-5-r1.patch:+ # importlib-metadata<5.0.0 salt-3005.1-r1.ebuild: "${FILESDIR}/salt-3005.1-importlib-metadata-5-r1.patch" salt-3005.3.ebuild: "${FILESDIR}/salt-3005.1-importlib-metadata-5-r1.patch" salt-3005.4.ebuild: "${FILESDIR}/salt-3005.1-importlib-metadata-5-r1.patch" I.e. no more dependency on dev-python/importlib-metadata (but importlib.metadata I suppose, would need to check).
Right.
