Bug 88647 - The package installer tool doesn't work properly.
Summary: The package installer tool doesn't work properly.
Keywords:
Status: CLOSED DUPLICATE of bug 78996
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: redhat-config-packages
Version: 9
Hardware: i686
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Jeremy Katz
QA Contact: David Lawrence
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2003-04-11 18:02 UTC by Noel Carneiro
Modified: 2007-04-18 16:52 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2006-02-21 18:52:37 UTC
Embargoed:


Attachments (Terms of Use)

Description Noel Carneiro 2003-04-11 18:02:04 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.77 [en] (X11; U; SunOS 5.7 sun4u)

Description of problem:
The default package manager program that is shipped with RH 9.0 doesn't show any
RPM package that is not within the distribution or is not in the default
categories. For instance, if you choose to install Opera or Wine after
installation, it does not show anywhere. Also, there is no GUI to manage RPM
packages!

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


How reproducible:
Always

Steps to Reproduce:
1.Install the distribuition normally.
2. After installation, try to install any other package not contained in the
distribution.
3.No mention of the program is shown.
    

Actual Results:  The package is installed, through a console rpm command or file
manager, but you cannot see it listed. If you want to upgrade or even uninstall
it, you have to do it manually in the console terminal.

Expected Results:  It should work with any RPM package.

Additional info:

The same problem applies when you update a package.

This problem has been reported for RH version 8.0

Comment 1 Jeremy Katz 2003-04-18 20:40:04 UTC

*** This bug has been marked as a duplicate of 78996 ***

Comment 2 Red Hat Bugzilla 2006-02-21 18:52:37 UTC
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.


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