looks like yum groupinfo <x> gives me this data.
On Tue, Jun 8, 2010 at 3:16 PM, Doug Reiland <[email protected]> wrote: > Hmm, i wasn't even close. > > Skipping missing group 'admin-tools' > Skipping missing group 'base' > Skipping missing group 'base-x' > Skipping missing group 'core' > Skipping missing group 'dial-up' > Skipping missing group 'fonts' > Skipping missing group 'gnome-desktop' > Skipping missing group 'graphical-internet' > Skipping missing group 'hardware-support' > Skipping missing group 'input-methods' > Skipping missing group 'office' > Skipping missing group 'printing' > Skipping missing group 'sound-and-video' > > Does anything exist that can parse a repo's comps.xml and list > packages in a group? I can feed this data to koji add-group-pkg. I > guess I should just add all the groups to my koji repo to prevent this > from occuring again. > > Doug > > On Tue, Jun 8, 2010 at 2:22 PM, Jay Greguske <[email protected]> wrote: >> It may. The package set in an F12-based kickstart file may not coincide with >> what is available in an F13 repo. Also, if the KS file has package groups, >> they may be getting skipped if your Koji repo does not define them. You >> would see evidence of that the log files: livecd.log or root.log. If @base >> or @core are getting skipped all sorts of fun stuff happens. >> >> - Jay >> >> >> ----- "Doug Reiland" <[email protected]> wrote: >> >>> thanks, >>> spin-kickstarts-0.12.1-1.fc12.noarch >>> >>> Note, my koji repo is f13-based if that matters. >>> >>> On Tue, Jun 8, 2010 at 1:56 PM, Jay Greguske <[email protected]> >>> wrote: >>> > What version of spin-kickstarts? I'll see if I can reproduce, I >>> haven't had this problem before. >>> > >>> > ----- "Doug Reiland" <[email protected]> wrote: >>> > >>> >> I have not been able to generate a working graphic iso >>> >> >>> >> Using /usr/share/spin-kickstarts stuff as examples. For example, >>> >> fedora-livecd-desktop.ks >>> >> >>> >> I copy this file and read in whatever %include there are so I have >>> 1 >>> >> .ks file. >>> >> >>> >> perfdm fails to start/crashses on boot. >>> >> >>> >> Any ideas? >>> >> >>> >> Note, I attended to "validated" the .ks file via revisor, but >>> revisor >>> >> gets hidden errors on any ks file after doing the mount >>> /dev/loop.... >>> >> -- >>> >> buildsys mailing list >>> >> [email protected] >>> >> https://admin.fedoraproject.org/mailman/listinfo/buildsys >>> > -- >>> > buildsys mailing list >>> > [email protected] >>> > https://admin.fedoraproject.org/mailman/listinfo/buildsys >>> > >>> -- >>> buildsys mailing list >>> [email protected] >>> https://admin.fedoraproject.org/mailman/listinfo/buildsys >> -- >> buildsys mailing list >> [email protected] >> https://admin.fedoraproject.org/mailman/listinfo/buildsys >> > -- buildsys mailing list [email protected] https://admin.fedoraproject.org/mailman/listinfo/buildsys
