Bug 1196651
Summary: | order of items in Software Selection should be deterministic and always the same | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Jan Sedlák <jsedlak> | ||||||
Component: | anaconda | Assignee: | Anaconda Maintenance Team <anaconda-maint-list> | ||||||
Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
Severity: | unspecified | Docs Contact: | |||||||
Priority: | unspecified | ||||||||
Version: | 22 | CC: | anaconda-maint-list, g.kaviyarasu, jonathan, kparal, lbrabec, vanmeeuwen+fedora | ||||||
Target Milestone: | --- | ||||||||
Target Release: | --- | ||||||||
Hardware: | Unspecified | ||||||||
OS: | Unspecified | ||||||||
Whiteboard: | |||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||
Doc Text: | Story Points: | --- | |||||||
Clone Of: | Environment: | ||||||||
Last Closed: | 2015-02-26 13:56:50 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
Jan Sedlák
2015-02-26 13:02:27 UTC
Created attachment 995574 [details]
Software Selection when using dnf
I think the interesting question here is whether anaconda does something to modify the order, or whether it takes it unaltered from yum/dnf. Second, whether the order provided by yum/dnf is somehow consistent and configured (and by whom?), or is it just a random representation of the underlying comps xml. And third, would anaconda consider sorting the list somehow (probably not just by alphabet, but also placing the most prominent Fedora flavors at the top), or do you not want to touch this? Thanks. There was a recent update for dnf to order comps by display_order, as yum does. If that turns out not have worked please reopen this bug. *** This bug has been marked as a duplicate of bug 1177002 *** |