Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 547736 - portage-2.2.18 remove search feature when installing ambiguous package or make it optional via config switch
Summary: portage-2.2.18 remove search feature when installing ambiguous package or mak...
Status: RESOLVED FIXED
Alias: None
Product: Portage Development
Classification: Unclassified
Component: Unclassified (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Portage team
URL:
Whiteboard:
Keywords: InVCS, REGRESSION
Depends on:
Blocks: 484436
  Show dependency tree
 
Reported: 2015-04-25 21:38 UTC by Sascha Nitsch
Modified: 2015-05-19 19:45 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Sascha Nitsch 2015-04-25 21:38:01 UTC
When doing an emerge -av <package> and the package is not already installed and the package name is ambiguous, a full search with the package name as search term is triggered.

Please remove this feature or at least make it triggered with an optional flag.
Currently this is coupled to --quiet which is just plain wrong.
Quickfix for now:
patch /usr/lib64/python<version>/site-packages/_emerge/depgraph.py
line 9035 from 
if "--quiet" in myopts:
if 1:

Reproducible: Always

Steps to Reproduce:
1. emerge --unmerge mc
2. emerge -av mc

Actual Results:  
a list of 107 packages containing "mc"

Expected Results:  
only the 2 conflicting names should be listed
as with emerge -av --quiet mc
!!! The short ebuild name "mc" is ambiguous. Please specify
!!! one of the following fully-qualified ebuild names instead:

    app-misc/mc
    sci-libs/mc


Portage 2.2.18 (python 2.7.9-final-0, default/linux/amd64/13.0, gcc-4.9.2, glibc-2.20-r2, 3.14.0-gentoo x86_64)
stripped other unneeded infos here.
Comment 1 Zac Medico gentoo-dev 2015-04-25 22:51:37 UTC
There's a patch in the following branch:

https://github.com/zmedico/portage/tree/bug_547736

I've posted it for review here:

https://archives.gentoo.org/gentoo-portage-dev/message/ef5dab944516f2b155181f6e1d694407
Comment 2 Sascha Nitsch 2015-04-25 23:01:43 UTC
Hi Zac,
I applied the patch and now the behavior is as expected.
As soon this is merged, the bug can be closed.
Comment 4 Brian Dolbec (RETIRED) gentoo-dev 2015-05-19 19:45:58 UTC
Released in portage-2.2.19