Summary: | sys-apps/portage: emerge --search --usepkg (or --getbinpkg) shows duplicate results | ||
---|---|---|---|
Product: | Portage Development | Reporter: | marco |
Component: | Core - Dependencies | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED FIXED | ||
Severity: | normal | Keywords: | InVCS |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 549914 |
Description
marco
2015-08-28 15:52:47 UTC
The issue is that the search._cp_all is passing an un-ordered iterator into MultiIterGroupBy. All of the iterators need to be ordered there. There's a patch in the following branch: https://github.com/zmedico/portage/tree/bug_559044 It can be installed like this: echo '=sys-apps/portage-9999 **' >> /etc/portage/package.accept_keywords portage_LIVE_BRANCH=bug_559044 \ portage_LIVE_REPO=https://github.com/zmedico/portage.git \ emerge -1 =sys-apps/portage-9999 I've posted it for review here: https://archives.gentoo.org/gentoo-portage-dev/message/809edbc9bc0409c89fd0d49bfb27a653 This is in the master branch: https://gitweb.gentoo.org/proj/portage.git/commit/?id=d87eeb7b8edf846330e3c2031eea2f326f149506 Patch tested and working :) . emerge --search iproute2 or emerge --search @sys-apps/iproute2 Local copy of remote index is up-to-date and will be used. [ Results for search key : @sys-apps/iproute2 ] Searching... * sys-apps/iproute2 Latest version available: 3.19.0 Latest version installed: 3.17.0 Size of files: 445 KiB Homepage: http://www.linuxfoundation.org/collaborate/workgroups/networking/iproute2 Description: kernel routing and traffic control utilities License: GPL-2 [ Applications found : 1 ] Now the Second problem ( ... The following binary packages have been ignored due to changed dependencies ...) on the test server disappeared after the new portage update. Do you think is better to rebuilt the @world packages on the builder server with the patched portage ? When do you think the patch can be included in the stable portage ? thanks (In reply to marco from comment #4) > Now the Second problem ( ... The following binary packages have been ignored > due to changed dependencies ...) on the test server disappeared after the > new portage update. That's a separate issue, and it's probably behaving as intended. You need to use --binpkg-changed-deps=n if you want to use binary packages with changed dependencies relative to the currently ebuilds available on your binhost client. > Do you think is better to rebuilt the @world packages on the builder server > with the patched portage ? This patch only affects emerge --search output, so there's no reason to do that. > When do you think the patch can be included in the stable portage ? I don't know when the next release will be. Released in portage-2.2.21 |