It seems that
Doesn't work for 5.5.0 Client, but works for Server.
David, can you please attach a kickstart which were used during the installation?
Could you also address the various questions in comment #4?
Well, then could you attach the error message you're seeing?
(In reply to comment #8)
> Well, then could you attach the error message you're seeing?
Something along the lines of being unable to resolve conflicts with the package set. Attempting to replicate this requires down time of a shared resource, which I'd like to avoid. If you could wait then I can provide a screenshot at some future time. In the meanwhile here's the snippet in the release note:
Previously, the kickstart installation method
offered two options to select all packages @Everything and * (wildcard).
As of Red Hat Enterprise Linux 5.5, both of these options have been
deprecated. Attempting to use a select all packages option will fail,
unless the kickstart file also includes package negation for conflicting
packages. Therefore, to install all packages but conflicting packages,
the kickstart file must contain:
Unfortunately there was no bug referenced in the release notes.
Is everyone here positive that their kickstart file lists nothing after -@conflicts? I have another bug (bug 577334) tracking that situation, and this one sounds awful similar to it. Please review that bug and the updates image described way at the bottom and compare this one to it.
Asnwering some questions:
1) The traceback from comment #15-#17 is bug 222513 and is not related to the package conflict.
2) AFAIK * should heva the same effect as @everything. Please use * for RHEL5 and later.
3) The bug count may differ for many reasons. The one that I see is that we have a bug in the everything-package-set test case which doesn't specify an installation key. Will correct it and schedule new tests against 5.5
Can you upload your anaconda.log so that we know which packages conflict?
Can you also investigate /tmp in stage2 and search for the comps.xml file there. and attach it as well.
please see comment #23. Is there anything we can do before 5.6 ?
cound the problem be in the fact that in Client -devel packages are in the Workstation/ repo instead of Client/ while for Server they are all in the Server/ repo?
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.