Bug 56047 – kpackage bad reporting rpm dependencies

Bug 56047 - kpackage bad reporting rpm dependencies

Summary:	kpackage bad reporting rpm dependencies

Status:	CLOSED RAWHIDE

Aliases:	None

Product:	Red Hat Linux
Classification:	Retired
Component:	kdeadmin (Show other bugs)
Sub Component:
Version:	7.2
Hardware:	i586 Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Bernhard Rosenkraenzer
QA Contact:	Ben Levenson
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2001-11-11 16:43 EST by Michal Vymazal
Modified:	2007-04-18 12:38 EDT (History)
CC List:	0 users

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2001-11-11 16:43:50 EST
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 Michal Vymazal 2001-11-11 16:43:45 EST

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i586; en-US; rv:0.9.4) Gecko/20010913

Description of problem:
The kpackage is bad reporting the rpm dependencies. It is found any
dependency, it no reports names of packages in this dependencies. When
installing, it is also looking for some source packages too and repoting
this as dependencies.

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


How reproducible:
Always

Steps to Reproduce:
1. Try to install some rpm package with kpackage.
2. It report some dependencies and you have to turn the dependency test to off.
3. After step 2 you can to install the package, but kpackage reports some
error first.
	

Additional info:

Comment 1 Bernhard Rosenkraenzer 2001-11-20 12:05:22 EST

Fixed in 2.2.2-1

Comment 2 Michal Vymazal 2001-11-21 14:43:17 EST

Well, I just installed kdeadmin-2.2.1-1 from rawhide and this problem is not
fixed here.

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