Bug 418251
| Summary: | Packages in RPM Groups are only shown for level 2 | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Gérard Milmeister <gemi> |
| Component: | yumex | Assignee: | Tim Lauridsen <tim.lauridsen> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | medium | Docs Contact: | |
| Priority: | low | ||
| Version: | 10 | CC: | triage |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2009-01-14 14:22:42 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Gérard Milmeister
2007-12-10 16:09:48 UTC
Just to make it clear.
There is two type of groups.
1. RPM Groups, multilevel groups defined in the rpm spec files. in yumex
select Category 'RPM Groups' in package view. Yumex can show packages on
lower levels (Ex. Development->Libraries->Java)
2. Comps Categories/Groups definded in the repo comps.xml files.
It is only contain 2 levels (1. Category, 2. Group). Subgroups is not
supported.
(In reply to comment #1) > There is two type of groups. > 1. RPM Groups, multilevel groups defined in the rpm spec files. in yumex > select Category 'RPM Groups' in package view. Yumex can show packages on > lower levels (Ex. Development->Libraries->Java) That's exactly the problem, it ONLY shows the lowest level. Ok, do you have any examples of packages not shown ? The packages in Development->Libraries->Java are shown, but those in Development->Libraries are not. This message is a reminder that Fedora 7 is nearing the end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 7. 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 '7'. 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 7'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 7 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. 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. If possible, it is recommended that you try the newest available Fedora distribution to see if your bug still exists. Please read the Release Notes for the newest Fedora distribution to make sure it will meet your needs: http://docs.fedoraproject.org/release-notes/ The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Ok, i found the problem, fixed upstream, will be available in yumex 2.0.5 This bug appears to have been reported against 'rawhide' during the Fedora 10 development cycle. Changing version to '10'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping |