Bug 1148436 - sugar kickstart has wrong identification in Fedora-Live-SoaS-x86_64-21_Beta-TC1
Summary: sugar kickstart has wrong identification in Fedora-Live-SoaS-x86_64-21_Beta-TC1
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: sugar
Version: 21
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
Assignee: Simon Schampijer
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: F21FinalFreezeException
TreeView+ depends on / blocked
 
Reported: 2014-10-01 13:12 UTC by satellitgo
Modified: 2014-10-15 19:33 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-10-03 10:55:41 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description satellitgo 2014-10-01 13:12:13 UTC 
Description of problem:
sugar kickstart has wrong identification in Fedora-Live-SoaS-x86_64-21_Beta-TC1

Version-Release number of selected component (if applicable):
Fedora-Live-SoaS-x86_64-21_Beta-TC1
fedora-livecd-soas-5664c40.ks

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:
Sugar on a stick (Unknown)
Fedora release 21 (rawhide)

Expected results:
Sugar on a stick 11
Fedora release 21
Additional info: (change this section of kickstart)
snip.....

# Get proper release naming in the control panel
cat >> /boot/olpc_build << EOF
Sugar on a Stick 11 (Unknown)
Fedora release 21 (Rawhide)
EOF

snip.....
Comment 1 Fedora Blocker Bugs Application 2014-10-01 13:18:12 UTC 
Proposed as a Freeze Exception for 21-final by Fedora user satellit using the blocker tracking app because:

 SoaS is not a blocking DE but it would be nice to have proper naming in the live.iso

A ....... package containing the correct names, information and repository configuration for a final Fedora release must be present on release-blocking images and the appropriately versioned .... package must be available in the release repository.
Comment 2 Peter Robinson 2014-10-03 10:55:41 UTC 
Committed a fix to soas kickstarts. Will be in the next builds
Note You need to log in before you can comment on or make changes to this bug.