Bug 8388 - Dependency errors
Dependency errors
Product: Red Hat Powertools
Classification: Retired
Component: gnome-games (Show other bugs)
i386 Linux
medium Severity high
: ---
: ---
Assigned To: Tim Powers
Depends On:
  Show dependency treegraph
Reported: 2000-01-11 19:00 EST by Joseph E. Kubany
Modified: 2008-05-01 11:37 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2000-01-13 14:34:09 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Joseph E. Kubany 2000-01-11 19:00:35 EST
I had 6.0 loaded then purchased and loaded the 6.1 upgrage. I have been
trying to load games from the power tools CD I received with 6.0. I get
many dependency errors, so I tried to load the libraries seperately. I
also get a lot of dependency errors loading the libraries. I am running
Gnome and then GnoRPM from the system startup menu. Will I be able to load
the applications on the power tools CD or will I have to wait until the
next release of Redhat Linux? Thank You, Joseph Kubany.
Comment 1 Tim Powers 2000-01-11 19:11:59 EST
Use the commandline instead of GnoRPM to install the packages. I noticed that
GnoRPM gives a lot of errors when it shouldn't since the commandline arguments
work fine ie. "rpm -Uvh <packagename>.rpm"

Comment 2 Tim Powers 2000-01-12 09:21:59 EST
This is not a bug with any packages in Powertools, it's a GnoRPM problem. I am
resolving this to not a bug.
Comment 3 Joseph E. Kubany 2000-01-13 00:32:59 EST
Tim: Is there a way to install all of the packages under a component? e.g.
games. Also, how would the XFrisk-(version 1.00,274k) be loaded? what is the
actual package name? page 42 power tools package list. Thank You, Joe
Comment 4 Tim Powers 2000-01-13 14:34:59 EST
Unfortunately you can't install packages by their groups. As far as the package
names, change directory into where the packages are located and let's say that
you want the true package name for XFrisk, do this while in the package

ls XFrisk*

This will display the full name of the package.


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