On Tue, Sep 11, 2012 at 10:13 AM, Eric Blake <eblake@xxxxxxxxxx> wrote: > On 09/11/2012 08:46 AM, Jeffrey Ollie wrote: >> After doing a yum upgrade on my desktop from F17 to F18, libvirtd >> would not start up (see below for the errors from the log) I grabbed >> libvirt 0.10.1-2 from koji and things are working now. Was there some >> other fix that would have gotten things working again? > > Just an unfortunate side effect of when alpha froze; where netcf and > libvirt have to be upgraded in lockstep to either both use libnl1 or > libnl3, but the freeze happened to catch netcf at libnl3 but libvirt at > libnl1. For more details, > https://bugzilla.redhat.com/show_bug.cgi?id=853381 Thanks for the explanation. >> Is there a >> reason that libvirt 0.10.1-2 hasn't been submitted as an update? > > It _has_ been submitted as an update; Unless I'm missing something, 0.10.1 doesn't appear at: https://admin.fedoraproject.org/updates/libvirt > it's just that updates-testing > can't be merged yet due to branching rules of the alpha freeze, without > declaring 853381 as an alpha blocker, but I don't think the blocker > rules apply to this one (IIRC, we don't have to self-host virtualization > until beta, at which point this would be a blocker). While updates that are in updates-testing wouldn't make it into the DVD or Live images, a yum upgrade like I did includes everything from updates-testing, and even if it didn't I would have enabled updates-testing after the F17->F18 upgrade. -- Jeff Ollie -- test mailing list test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
