Summary: | Inconsistant wildcard behavior in 'emerge search' command. | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Michael Gayeski <gayeski> |
Component: | Unclassified | Assignee: | Daniel Robbins (RETIRED) <drobbins> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | gayeski |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Michael Gayeski
2002-04-09 02:44:27 UTC
"*" should be ".*", reassiging to Geert. Geert, when you have time can you fix this? Yes, i can confirm this bug. emerge crashes and displayes a traceback. More test cases: emerge -s "*""<enter>(bash displayes PS2 prompt)"<enter> -crash emerge -s "*""" -works emerge -s "*"x -crash, replace x with anything other than a space. This could also be a security concern. A properly hacked string could crash emerge and compramize the system. this works in portage-1.9.2 never mind -- I did it from /root, so it used all the entries in my root dir as the search options. That item should probably be removed from the help Will be fixed in 1.9.5 |