Bug 505262
Summary: | F11 kickstart files still pointing to rawhide repos! | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | James Heather <drfudgeboy> |
Component: | spin-kickstarts | Assignee: | Jeroen van Meeuwen <vanmeeuwen+fedora> |
Status: | CLOSED NEXTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | high | Docs Contact: | |
Priority: | low | ||
Version: | 11 | CC: | axet, kjell, mads, swu98, valent.turkovic, vanmeeuwen+fedora |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2009-06-20 17:35:38 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: | |||
Bug Depends On: | |||
Bug Blocks: | 630317 |
Description
James Heather
2009-06-11 09:00:24 UTC
*** Bug 506134 has been marked as a duplicate of this bug. *** Bug confirmed/triaged. It is fixed "upstream" in http://git.fedorahosted.org/git/spin-kickstarts.git?p=spin-kickstarts.git;a=commitdiff;h=f3bdc1672b1f91f9e9ec143f6039c4ec033f1add;hp=3e28840706c73680c60e8cfa8011be71745688f3 The package description says that it is for creating customized spins, not that it is for creating spins of rawhide. So I would expect the kickstart files in any "branch" (released or rawhide) to build spins of exactly the same branch, and that spin-kickstarts thus should be in sync with the yum repos in fedora-release, ideally by making updating spin-kickstarts a step in the Fedora release process. I don't know if that is a valid expectation? Yes, this should have been fedora-11 repos. Building a new package now. Give https://admin.fedoraproject.org/updates/spin-kickstarts-0.11.4-1.fc11 a boost if you like what you see there. *** Bug 507213 has been marked as a duplicate of this bug. *** *** Bug 507301 has been marked as a duplicate of this bug. *** *** Bug 507488 has been marked as a duplicate of this bug. *** |