Bug 852240
Summary: | yum doesn't merge/generate comps environment data | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Jesse Keating <jkeating> |
Component: | yum | Assignee: | Fedora Packaging Toolset Team <packaging-team> |
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 18 | CC: | awilliam, dcantrell, dennis, dwa, ffesti, hamzy, maxamillion, notting, packaging-team, robatino, tim.lauridsen, zpavlas |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | AcceptedBlocker | ||
Fixed In Version: | yum-3.4.3-36.fc18 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2012-08-31 06:45:09 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: | |||
Bug Depends On: | |||
Bug Blocks: | 752654, 846989 |
Description
Jesse Keating
2012-08-28 01:04:49 UTC
Also note that if there is a blank software selection spoke, the spoke is considered "incomplete", which means installation cannot proceed. Proposing as Alpha blocker: this violates criterion "When booting from a DVD ISO image, the installer must be able to use the DVD local package source options". Tracked this down to a yum issue, patch generated and submitted. http://lists.baseurl.org/pipermail/yum-devel/2012-August/009536.html *** Bug 852050 has been marked as a duplicate of this bug. *** Discussed at 2012-08-29 blocker review meeting. Accepted as a blocker per criterion "When booting from a DVD ISO image, the installer must be able to use the DVD local package source options". This does raise another question - where does this merged comps file end up? Is it also dropping all anaconda whitelist/blacklist, and langpack info? (In reply to comment #6) > This does raise another question - where does this merged comps file end up? > Is it also dropping all anaconda whitelist/blacklist, and langpack info? The merged comps gets written out and used to generate the repodata on the DVD and in the Fedora/os/ directory created by the pungi run. I have no idea about the whitelist/blacklist or langpack data. Is there examples of this in the comps file in git? See the 'langpacks', 'whiteout', and 'blacklist' sections at the end of comps-XYZ.xml(.in). And yes, I've confirmed they are missing in the 'Fedora' tree (and presumably the DVD) while existing in the 'Everything' tree. yum-3.4.3-39.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/FEDORA-2012-12900/yum-3.4.3-39.fc18 (In reply to comment #8) > See the 'langpacks', 'whiteout', and 'blacklist' sections at the end of > comps-XYZ.xml(.in). And yes, I've confirmed they are missing in the 'Fedora' > tree (and presumably the DVD) while existing in the 'Everything' tree. So the fix for getting environment stuff was in yum itself, in the comps.py Comps.write() method. Most the wiring was there for it, just needed to be hooked up. Question is, does the wiring exist for the other items, or is this going to be a much bigger task... A quick git grep shows that yum doesn't really have much info at all on langpack, whiteout, or blacklist, at least in relation to comps. Time for a new bug I guess. yum-3.4.3-40.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report. |