While have: $ emerge -pq python:3.10 python:3.11 [ebuild R ] dev-lang/python-3.10.5 [ebuild R ] dev-lang/python-3.11.0_beta3 With portage-utils-0.93.3 I get: $ qlist -Iv ">=dev-lang/python-3.10.0_p1-r1:3.10" dev-lang/python-3.10.5 $ qlist -Iv ">=dev-lang/python-3.10.0_p1-r1:3.11" # bumped slot dev-lang/python-3.11.0_beta3 With portage-utils-0.94: $ qlist -Iv ">=dev-lang/python-3.10.0_p1-r1:3.10" (nothing) $ qlist -Iv ">=dev-lang/python-3.10.0_p1-r1:3.11" # bumped slot dev-lang/python-3.11.0_beta3 But juippis noted that this works for some reason (dropped _p1-r1) $ qlist -Iv ">=dev-lang/python-3.10.0:3.10" dev-lang/python-3.10.5 Originally reported as a app-portage/iwdevtools issue by juippis, aka end up getting messages like: * qa-vdb: running 'qa-vdb' failed (disable with QA_VDB=n) * Error: no installed provider in vdb for '>=dev-lang/python-3.10.0_p1-r1:3.10' (may be due to binpkgs ordering / --nodeps / package.provided) (qa-vdb:vdb-get_deps:374)
From git bisect, seems caused by: https://gitweb.gentoo.org/proj/portage-utils.git/commit/?id=7de2f154c775e9de276f2fc1f619922f48a13b90
hmmmm :(
feels the bug lies in here: d% qatom -s dev-lang/python-3.10.5 ">=dev-lang/python-3.10.0_p1-r1" dev-lang/python-3.10.5 != >=dev-lang/python-3.10.0_p1-r1 % qatom -s dev-lang/python-3.10.5 ">=dev-lang/python-3.10.1_p1-r1" dev-lang/python-3.10.5 == >=dev-lang/python-3.10.1_p1-r1 The "0" smells like 3.3:1-8, but it should probably be seen as 3.3:9.
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/proj/portage-utils.git/commit/?id=62503bbd9e82a5b0fdeec6e357a95e724ec3cef6 commit 62503bbd9e82a5b0fdeec6e357a95e724ec3cef6 Author: Fabian Groffen <grobian@gentoo.org> AuthorDate: 2022-06-15 19:53:43 +0000 Commit: Fabian Groffen <grobian@gentoo.org> CommitDate: 2022-06-15 19:53:43 +0000 libq/atom: fix atom_compare for "0" version components Bug: https://bugs.gentoo.org/852197 Signed-off-by: Fabian Groffen <grobian@gentoo.org> libq/atom.c | 36 ++++++++++++++++++++++++++---------- tests/atom_compare/static.good | 1 + tests/atom_compare/static.tests | 1 + 3 files changed, 28 insertions(+), 10 deletions(-)
Thanks for the quick fix, seems to work. Been getting this on a few other atoms since too like ">=dev-libs/libffi-3.0.13-r1" also having a .0 but that works fine for that too now. Would it be possible to get this in-tree soon? (or a 0.94 mask works for me too if don't want to rush it). Given devs tend to use ~arch imagine getting these errors all over.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=b2c60021fe098bf7d3b3d3888de1aad5605da14a commit b2c60021fe098bf7d3b3d3888de1aad5605da14a Author: Fabian Groffen <grobian@gentoo.org> AuthorDate: 2022-06-16 06:03:02 +0000 Commit: Fabian Groffen <grobian@gentoo.org> CommitDate: 2022-06-16 06:03:43 +0000 app-portage/portage-utils-0.94.1: bugfix for 0.94 release Closes: https://bugs.gentoo.org/852197 Signed-off-by: Fabian Groffen <grobian@gentoo.org> app-portage/portage-utils/Manifest | 2 +- .../{portage-utils-0.94.ebuild => portage-utils-0.94.1.ebuild} | 0 2 files changed, 1 insertion(+), 1 deletion(-)
Thank you for the swift action \o/
thank you for the extensive report and confirming the fix, sorry for the noise
