When an ambiguous package is passed to the uninstall command (emerge --unmerge/--depclean), the output is exactly the same as when the package doesn't exist. Reproducible: Always Steps to Reproduce: 1.Run an uninstall (depclean or unmerge) command on a term matching multiple fully-qualified installed ebuild names, e.g.: >$ emerge --ask --depclean man Actual Results: The output describing the error is in the following format: >--- Couldn't find 'man' to depclean. Expected Results: The output should contain information similar to the output of install command in similar situation; e.g. based on `emerge --quiet man`: >--- !!! The short ebuild name "man" is ambiguous. Please specify >--- !!! one of the following fully-qualified ebuild names instead: >--- >--- acct-group/man >--- acct-user/man >--- virtual/man (Naturally, the output should only contain already installed packages.)
Created attachment 898148 [details, diff] Patch to add ambiguous package handling to unmerge Something like this? Maybe there's a better way than search() though...
>Something like this? Perhaps?… It's hard to tell for sure without seeing the actual output. …Though I doubt it makes sense to have two subsequent `if not mymatch:` blocks (especially as the 1st one ends with a `sys.exit()` call) >Maybe there's a better way than search() though... I mean, this logic is already implemented elsewhere, so it can probably be reused directly (or failing that, copy-pasted). P.S. I think I've also seen someone mention that this bug may be limited to _some_ packages (e.g. unmerge cannot match `man` but has no problem matching `git`)
