Bug 893858 - spin-kickstarts build that matches final F18 compose required for F18 release
Summary: spin-kickstarts build that matches final F18 compose required for F18 release
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: spin-kickstarts
Version: 18
Hardware: All
OS: All
unspecified
high
Target Milestone: ---
Assignee: Jeroen van Meeuwen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: AcceptedBlocker
Depends On:
Blocks: F18Blocker, F18FinalBlocker
TreeView+ depends on / blocked
 
Reported: 2013-01-10 03:54 UTC by Adam Williamson
Modified: 2013-01-10 05:43 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-01-10 05:43:25 UTC


Attachments (Terms of Use)

Description Adam Williamson 2013-01-10 03:54:12 UTC
In the Final criteria:

"A spin-kickstarts package which contains the exact kickstart files used to build the release must be present in the release repository. The included kickstarts must define the correct set of release repositories"

Since we've signed off on either RC3 or RC4 (which were built with the same kickstarts), we know the final kickstart set for definite. I've built spin-kickstarts-0.18.3-1.fc18 with the final F18 kickstart set. We just have to push it stable before mirroring. Nominating as a blocker, but this doesn't mean our composes are bad, just that we have to push this spin-kickstarts stable.

Comment 1 Fedora Update System 2013-01-10 03:56:22 UTC
spin-kickstarts-0.18.3-1.fc18 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/spin-kickstarts-0.18.3-1.fc18

Comment 2 Tim Flink 2013-01-10 04:19:32 UTC
+1 blocker per criterion cited in description

Comment 3 Kevin Fenzi 2013-01-10 04:20:56 UTC
+1 blocker. ditto.

Comment 4 Adam Williamson 2013-01-10 05:29:43 UTC
Accepted as a blocker.

Comment 5 Fedora Update System 2013-01-10 05:43:29 UTC
spin-kickstarts-0.18.3-1.fc18 has been pushed to the Fedora 18 stable repository.  If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.