Bug 208426 – fedora-extras packages don't always show up in pirut

Bug 208426 - fedora-extras packages don't always show up in pirut

Summary:	fedora-extras packages don't always show up in pirut

Status:	CLOSED NOTABUG

Aliases:	None

Product:	Fedora
Classification:	Fedora
Component:	pirut (Show other bugs)
Sub Component:
Version:	rawhide
Hardware:	All Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Jeremy Katz
QA Contact:
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2006-09-28 10:52 EDT by Armijn Hemel
Modified:	2007-11-30 17:11 EST (History)
CC List:	0 users

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2006-09-28 10:56:44 EDT
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Armijn Hemel 2006-09-28 10:52:19 EDT

Description of problem:

Some packages from Fedora Extras don't show up in pirut, for example Wine. They
can be found using "Search" and "List", but not using "Browse". The Wine package
falls into the "Applications/Emulators" category, which does not exist. Other
packages from Extras, such as xmms *can* be found using "Browse".

Version-Release number of selected component (if applicable):

pirut-1.1.16-1

How reproducible:

Always

Steps to Reproduce:
1. launch pirut
2. browse for wine and xmms
3.
  
Actual results:

xmms can be found, wine cannot

Expected results:

All packages from Fedora Extras should be found.

Additional info:

it seems like categories which are specific to just Fedora Extras don't show up
in the "Browse" menu.

Comment 1 Jeremy Katz 2006-09-28 10:56:44 EDT

The group tag in the package isn't used -- the useful information is where an
application lives in the comps file.

Note You need to log in before you can comment on or make changes to this bug.