Bug 1416518
Summary: | anaconda kickstart should ignore package conflicts instead of crashing in transaction check | ||||||
---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Edgar Hoch <edgar.hoch> | ||||
Component: | anaconda | Assignee: | Anaconda Maintenance Team <anaconda-maint-list> | ||||
Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
Severity: | low | Docs Contact: | |||||
Priority: | unspecified | ||||||
Version: | 25 | CC: | anaconda-maint-list, g.kaviyarasu, jonathan, mkolman, vanmeeuwen+fedora, vponcova | ||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
Hardware: | Unspecified | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | If docs needed, set a value | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2017-12-12 10:45:41 UTC | Type: | Bug | ||||
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
Edgar Hoch
2017-01-25 16:52:46 UTC
Created attachment 1244318 [details]
kickstart file (without sensitive data)
I found by try and error that package polymake causes the error described above. See bug #1415548 . I think, in this case anaconda should either exclude both packages, or try to find the packages with causes the dependency error and excludes these, or try to determine which packages are mandatory, default and optional and exclude first the optional packages, then the default and at last the mandatory packages from the installation list. Anaconda should try to install the system with the best (greatest?) set of packages from the kickstart file - ignored packages can be installed later. It is much simpler for an admin to install packages on a running system and to search for dependency errors than trying to find the error in a crashed kickstarted system! Moreover the error message of anaconda doesn't show the package that really causes the dependency error! Note: Excluding polymake in kickstart file ks.cfg with the line -polymake was not sufficient to resolve the dependencies. Anaconda has still included polymake in the package installation list (I didn't find out why) and ignores my exclude direction! I have replaced @engineering-and-scientific --optional with @engineering-and-scientific now kickstart installs without this error. I guess that other optional packages of group engineering-and-scientific require polymake... In this case anaconda should also exclude packages that require polymake (the package causing the conflicting package versions of vim-minimal and vim-common). I know this is not a trivial algorithm... FYI: After installation was done as in comment #3 I did the following: # dnf group mark remove engineering-and-scientific # dnf group install with-optional engineering-and-scientific This told me which packages will be skipped because of conflicts. Now I had build a new kickstart file with the following exclusions. Kickstart installation has run successful with this configuration. @engineering-and-scientific --optional -Singular -libqhull_r -ocaml-tplib-tools -polymake -qepcad-B -qhull -saclib -surf-geometry -sympol-libs I want to mention that I see a similar problem in dnf. For example, if you want to install all python packages, and want to use dnf -y install 'python*' this will not work. dnf terminates with file conflict errors similar to the description of this bug. In both cases the error occurs in the transaction check, after dnf or anaconda has selected the list of packages to install. But crashing is still not a good solution. Maybe that dnf and anaconda has to go back a step and do package selection again, excluding conflicting packages (as described in comment #2)? Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 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. |