Hide Forgot
Description of problem: Fire up yumex. Select "all". - Type "stdc" in the search window: Returns a number of stdc++ and compat-stdc++ packages. - Type "stdc+" in the search window: Returns nothing. - Type "stdc++" in the search window: Returns only two stdc++ packages. (Seems to zap anything that doesn't end with '+') Expected results: Assuming that yumex' search functions doesn't support regex - stdc, stdc+ and stdc++ should all return the same number of results. (All the packages that have stdc/+/++ in their name) - Gilboa
Fixed upstream, will be available in yumex 2.0.5.
This message is a reminder that Fedora 8 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 8. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '8'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 8's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 8 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
As this bug is in MODIFIED, Fedora believes that a fix has been committed that resolves the problem listed in this bug report. If this is not the case, please re-open this report, noting the version of the package that you reproduced the bug against. Thanks for the report!