On my system x11-libs/qt-3.3.4-r2 is installed but is missing from portage tree. The bug I experience (triggered by this situation) is that equery uses qt doesn't work. And it could be made to work since the ebuild is present in /var/db/pkg. This is related to #71737, but different, as there the reporter wants to perform queries on not-installed packages, while I want to perform query on ebuilds missing from portage tree. My gentoolkit version: # equery list gentoolkit [ Searching for package 'gentoolkit' in all categories among: ] * installed packages [I--] [ ] app-portage/gentoolkit-dev-0.2.5 (0) [I--] [ ] app-portage/gentoolkit-0.2.0-r2 (0) The output I got is below: # equery list qt; equery uses qt; ls /var/db/pkg/x11-libs/qt-3.3.4-r2/ [ Searching for package 'qt' in all categories among: ] * installed packages [I--] [M ] x11-libs/qt-3.3.4-r2 (3) [ Searching for packages matching qt... ] [ Colour Code : set unset ] [ Legend : Left column (U) - USE flags from make.conf ] [ : Right column (I) - USE flags packages was installed with ] !!! No installed packages found for qt ASFLAGS CDEPEND COUNTER DEPEND EXTRA_EMAKE LDFLAGS PDEPEND qt-3.3.4-r2.ebuild USE CATEGORY CFLAGS CTARGET environment.bz2 FEATURES LIBCFLAGS PF RDEPEND CBUILD CHOST CXX EXTRA_ECONF INHERITED LIBCXXFLAGS PKGUSE RESTRICT CC CONTENTS CXXFLAGS EXTRA_EINSTALL IUSE LICENSE PROVIDE SLOT Reproducible: Always Steps to Reproduce: 1. 2. 3.
This is the same as bug #71737 *** This bug has been marked as a duplicate of 71737 ***
I even added a reference to 71737, but as I noted, it's a different story. The problem I mentioned is described starting from comment 6, but is different to the main thread (some other comments before _may_ refer to this problem). In fact, their main problem can be workarounded using -a (they want to do query for uninstalled packages, when the ebuild exist). I, and author of comment 6, want to perform queries on installed packages whose ebuilds are only in /var/db/pkg and not in /usr/portage. It's different. However, I'm leaving it marked as DUPLICATE, for now... you may still want to fix them together.
I understand the differences in the cases presented. However, it is the same bug in the equery code that is causing the problem.
