Bug 288551 – sys-apps/portage portageq metadata has bad output formatting when an unqualified package name is given that has multiple category choices

• Product: Portage Development
• Status: RESOLVED FIXED

[Description Mart Raudsepp 2009-10-11 12:28:13 UTC]

As talked on IRC a few days ago to file a bug about this:

I was playing around with "portageq metadata / ebuild glibc IUSE" to check about nptl USE flag, but got this output instead:

$ portageq metadata / ebuild glibc IUSE
You specified an unqualified atom that matched multiple packages:
* n
* e
* e
* d
*  
* m
* o
* r
* e
*  
* t
* h
* a
* n
*  
* 1
*  
* v
* a
* l
* u
* e
*  
* t
* o
*  
* u
* n
* p
* a
* c
* k

Please use a more specific atom.



That's because I use crossdev and have multiple glibc packages (sys-devel and various cross-* category ones). Same happens with e.g "portageq metadata / ebuild git IUSE"

Using glibc atom for "portageq has_version" gives a better output as an example:

$ portageq has_version / glibc
You specified an unqualified atom that matched multiple packages:
* cross-i486-pc-linux-gnu/glibc
* cross-i686-pc-linux-gnu/glibc
* sys-libs/glibc

Please use a more specific atom.


I don't know if some other portageq commands might not have a similar problem as "metadata".

[Comment 1 Zac Medico 2009-10-11 23:07:29 UTC]

Thanks, this is fixed in svn r14579.

[Comment 2 Zac Medico 2009-10-12 07:04:21 UTC]

This is fixed in 2.1.7.1 and 2.2_rc46.