Hide Forgot
Created attachment 831881 [details] ks.cfg - relative small kickstart file used for my test installation Description of problem: I tried to make a test installation with F20 TC3 and got package conflict errors when using kickstart with %packages --multilib . I think this is a severe error, as it breaks kickstart installation. Some days ago I created bug #1033870. I wanted to isolate the problem and stripped down my kickstart file. I reduced my test kickstart file to only contain a minimal set of packages: %packages --ignoremissing --default --multilib --instLangs=de @ standard --optional %end I have attached my test kickstart file and the packaging.log file of the test installation. I removed our local network names and addresses for privacy. I have used pxe to boot. There seems something wrong with multilib and Fedora 20. I don't know which component of Fedora 20 is the right one for this bug report, so I have used anaconda because it seems that more than one package is affected. Version-Release number of selected component (if applicable): Fedora 20 TC3 How reproducible: Always. Steps to Reproduce: 1. Modify the kickstart file attached and enter your local network data for kickstart installation. 2. Use the F20 TC3 and the modified kickstart file and do a kickstart installation. Actual results: Kickstart installation stopps with package conflict errors. See file packaging.log. Expected results: No errors, successful kickstart installation. Additional info: - When I have removed "--multilib" from the attached kickstart file and have used this for kickstart installation, no error has occured. - When I have used the attached kickstart file with Fedora 19 (and the path to Fedora 19 installation dvd in the kickstart file) to install Fedora 19, no error has occured.
Created attachment 831882 [details] packaging.log - package log file of kickstart installation with error messages
The multilib problem still exists with Fedora 20 x86 release.
This is a problem in the packages themselves. It looks like the libbluray issue has been fixed. Assigning to tracker.
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.