Bug 222760

Summary:	Group View does not always work when one or more repos don't maintain comps.xml
Product:	[Fedora] Fedora	Reporter:	Stewart Adam <s.adam>
Component:	yumex	Assignee:	Tim Lauridsen <tim.lauridsen>
Status:	CLOSED UPSTREAM	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	6
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:	2007-06-12 07:58:33 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 Stewart Adam 2007-01-16 00:02:56 UTC

Description of problem:
I'm not sure, but I think this problem is more easily reproduced when one repo
or more doesn't maintain a comps.xml, the Group view shows little or no
packages. Sometimes, a group will contain packages but have an empty name.

Version-Release number of selected component (if applicable):
yumex-1.2.2-1.0.fc6

How reproducible:
Sometimes

Steps to Reproduce:
1. Use various mixes of repos
2. Look at the Group View
  
Actual results:
See Description

Expected results:
Groups with no name go under 'Unknown' or 'Other', and packages are correctly
populated into each group.

Comment 1 Tim Lauridsen 2007-03-21 13:23:37 UTC

This is caused by some repos (Like Livna) dont use name tags in comps xml,
because they want to use the same name an description as the comps.xml in core.
I have submit a fix to yum upstream cvs (3.1.x), it will be included in
yum-3.1.5 for FC7.