Bug 580947

Summary: @everything file conflicts
Product: Red Hat Enterprise Linux 5 Reporter: Thomas Zine <tzine3>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED DUPLICATE QA Contact: Release Test Team <release-test-team-automation>
Severity: low Docs Contact:
Priority: low    
Version: 5.5Keywords: Reopened
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-04-26 16:10:10 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Log of failures
none
Work around
none
log with -@Conflicts none

Description Thomas Zine 2010-04-09 14:47:19 UTC
Created attachment 405562 [details]
Log of failures

Description of problem:
When kickstart file contains
%packages
@everything

file conflicts emerge. broke down packages from doing a manual selection and removing @everything. This worked fine in previous versions 5.4 and 5.3.

Version-Release number of selected component (if applicable):
5.5 Server x64, x86; Workstation x64 x86, 

How reproducible:
always

Steps to Reproduce:
1. add @everything to %packages in kickstart file
  
Actual results:


Expected results:


Additional info:

Comment 1 Thomas Zine 2010-04-09 14:50:13 UTC
Created attachment 405563 [details]
Work around

Comment 2 Chris Lumens 2010-04-09 15:10:02 UTC
You need to add -@Conflicts to your kickstart file.  This is mentioned in the 5.5 release notes.

Comment 3 Thomas Zine 2010-04-26 15:58:34 UTC
Created attachment 409219 [details]
log with -@Conflicts

Comment 4 Thomas Zine 2010-04-26 15:59:36 UTC
adding -@Conflicts as directed still fails.

%packages
@everything
-@Conflicts
grub
kernel
kernel-devel
kexec-tools
e2fsprogs

Comment 5 Chris Lumens 2010-04-26 16:10:10 UTC

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