|
Bugzilla – Full Text Bug Listing |
| Summary: | yast2 incorrectly gives no results | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 13.1 | Reporter: | Forgotten User SpTvqxsYZX <forgotten_SpTvqxsYZX> |
| Component: | YaST2 | Assignee: | Ladislav Slezák <lslezak> |
| Status: | RESOLVED INVALID | QA Contact: | Jiri Srain <jsrain> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | jreidinger |
| Version: | Final | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Forgotten User SpTvqxsYZX
2014-02-14 03:25:56 UTC
I suppose you are talking about the Qt frontent. Yast takes the input as one word so "lib client0" is used literally as written. And that is obviously not found. And "lib*client0" is wrong regular expression, it would match e.g. "libbbbclient0" or "liclient0" - so again no match. The correct regexp is "lib.*client0", that works for me. Or you can switch to Wild Card matching and use "lib*client0" (like in shell) - that also works correctly. Can you explain why it would not search individually for lib and client0 terms as it should instead of interpreting the space litterally? I don't think package names can even have spaces, so it makes sense to fix it not searching of each word, like other package managers such as synaptic does. |