Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 903407

Summary: Add a small piece to the FC18 kickstart pages about group names
Product: [Retired] Fedora Documentation Reporter: Brendan Minish <bminish>
Component: install-guideAssignee: Petr Bokoc <pbokoc>
Status: CLOSED CURRENTRELEASE QA Contact: Ruediger Landmann <rlandman+disabled>
Severity: low Docs Contact:
Priority: unspecified    
Version: develCC: pbokoc, rlandman, zach
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-07-25 15:15:30 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:
Attachments:
Description Flags
comps file, containing group list none

Description Brendan Minish 2013-01-23 22:33:11 UTC
User-Agent:       Mozilla/5.0 (X11; Linux x86_64; rv:18.0) Gecko/20100101 Firefox/18.0
Build Identifier: 

Upgrading from FC17 to FC18 has also required that I alter my kickstart files, particularly in the area pertaining to package groups as some names have changed between fc17 and fc18 

I was having a hard time working out what the correct group names were for use in kickstart files until someone on #fedora showed me the following yum command 
yum grouplist hidden -v

I suggest adding a line or two about this to the following page since at present groups are discussed in some detail but there is no canonical list of group names given. 
Also I had to use names like kde-desktop in my kickstart file rather than 'KDE Plasma Workspaces' 

Aim here is to make it a bit easier for the creator of kickstart files to get up and running easily 


Reproducible: Always




Hope this is a helpful suggestion ;-)

Comment 1 Jack Reed 2013-03-28 05:59:53 UTC
Created attachment 717442 [details]
comps file, containing group list

Comment 2 Jack Reed 2013-03-28 06:00:27 UTC
Thanks for the suggestion, Brendan. That is indeed a helpful command. I'm actually not sure if 'hidden' is even required, but it may be due to my particular configuration that I receive the same output in each case.

Regardless, have you taken a look at the variant/repodata/comps-*.xml file in the DVD ISO, as referenced in 15.5. Package Selection? 

(The filename is actually incorrect, as comps is preceded by a string of assorted characters, but it's easy to find in that directory. I'll update the filename to *-Fedora-18-comps.xml). 

The file contains a comparable number of groups to the grouplist command, which can be browsed by looking for the groupid tag, as suggested by "Each group has an id, user visibility value, name, description, and package list", although I can make this clearer.

Pointing users to this file within the ISO rather than suggesting a yum command seems more efficient because they may not have a system to execute the command on, although I admit the file is not as readable as the grouplist output. 

Plus, this section also explains that "package selection during upgrades is not supported", and upgrades are a case where the user would be able to execute a yum command.

I've attached the comps file from the F18 ISO (you can see the kde-desktop package in there). Let me know if you this suffices for your use case. However, if this less direct method was what you were hoping to remedy, I can look into adding the command and word a proviso to tie into the fact that package selection during upgrades is not supported.

Comment 4 Brendan Minish 2013-06-17 11:59:32 UTC
The XML file is helpful also, thanks for pointing that out.
I ran across this issue as I was modifying existing Kickstart files to deal with the changes in F18.

Some may be making kickstart files from scratch for completely fresh installs but I suspect most will either be creating kickstart from anaconda-ks.cfg or modifying existing files.

It's probably worth having a couple of lines in documentation that mention both sources for getting the required group names since the desired goal in documentation is presumably to make task of creating kickstart files as easy as possible regardless of the user's starting position.

If you have a working install already, then the yum command is easier than digging through the XML, However for a fresh install the XML data is available.

Comment 5 Petr Bokoc 2013-06-28 17:52:07 UTC
Added a mention of the yum grouplist hidden -v command into section 15.5. Package Selection.

Changes are in commit 2be6a18d53c03f0578b8e2032254b3c18448d9f8.