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
