On Thu, 2007-10-04 at 13:25 -0600, Orion Poplawski wrote: > I do F7 kickstart installs here and I add a repo line for the F7 updates > so that they get installed automatically. Today I get an error from > anaconda complaining that it can't find the comps-f7.xml file, though it > does download it fine. I'm guessing that it is actually a parsing > error, though no diagnostics make it into anaconda.log. I did a > successful install on the 1st, so the change must be recent. To give a little more detail, there was a bug with comps file creation for today's updates so the file didn't match the checksum. Pup will catch this problem (yay!), but it gives you a completely unhelpful error message "unable to start due to a configuration error", with a Details box containing: "None". Oops. Like Jeremy said, it should be fixed as soon as the updates are finished being pushed/synched. Also I'm pretty sure that pup in rawhide/F8 will give you a more helpful message, so if it happens again in the future things should be a little less confusing. -w
Attachment:
signature.asc
Description: This is a digitally signed message part
-- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list