Red Hat Bugzilla – Bug 206161
Many dependency warning issued after selecting s/w for installation
Last modified: 2007-11-30 17:07:33 EST
Description of problem:
In installing the desktop client version for x86-64, I selected every option for
additional software, except web server. When I look at the screen contents on VT
#3(ctrl-alt-F3), I see lots and lots of warnings about dependency for a lot of
It also takes more than a minute before the "next" key is enabled.
Version-Release number of selected component (if applicable):
How reproducible: 100%
Steps to Reproduce:
1. Use x86-64 client install DVD
2. Install using "D" for Desktop client
3. Select first two categories of software(window manager & development?), but
don't select "web server"
4. Select every optional component under both selected categories
5. Select "next"
6. ctrl-alt-F3 to view VT3's contents
Actual results: many, many dependancy warnings
Expected results: No dependency warnings
Here are a couple of additions/corrections to "Steps to Reproduce":
In step #3, I selected the categories "Office & Productivity" & "Software
After #3, I selected "customize now" and proceeded to select all of the
components(step #4) listed for each of the first 5
options(Desktop/Applications/Development/Servers/BaseSystem) but added nothing
Please post an example of the sorts of messages you are seeing, as there are a
variety of dependancy messages that can appear in the logs.
Unless there's a log somewhere which captures messages posted prior to
installation, which I doubt there is, there's no good way to capture messages
like this other than to manual copy them down.
There's /tmp/anaconda.log at install-time which gets copied to
/var/log/anaconda.log on the installed system.
Created attachment 136098 [details]
/var/log/anaconda.log file from test machine
Packages that are dep required are only present in the Workstation variant.
Need to have clean rpm verifies (i.e. no missing deps) QE ack for B2. See
section 9c of the release criteria.
A package has been built which should help the problem described in
this bug report. This report is therefore being closed with a resolution
of CURRENTRELEASE. You may reopen this bug report if the solution does
not work for you.