On 09/11/2012 11:13 AM, Eric Blake 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. Actually, I don't think that's correct. From what I can see, netcf in the F18 stable repo is at 0.1.9-1, which is still using libnl1. It's only people who are using the updates-testing repo that will get the newer netcf-0.2.2-1, which links against libnl3. (I've requested that netcf-0.2.2-1 be promoted to stable, but that won't happen until the freeze is lifted). > For more details, > https://bugzilla.redhat.com/show_bug.cgi?id=853381 > >> Is there a >> reason that libvirt 0.10.1-2 hasn't been submitted as an update? > It _has_ been submitted as an update; 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). Nope. libvirt-0.10.1-2 hasn't been submitted as an update, and isn't in updates-testing yet. If that was done, then at least all of the repos would be internally consistent - the packages for alpha would be libvirt-0.10.0rc0-1 and netcf-0.1.9-1 (both linking against libnl-1.1), and the packages in updates-testing would be libvirt-0.10.1-2 (or possibly a newer build) and netcf-0.2.2-1 (both linking against libnl-3). This would eliminate problems for everyone except those manually updating individual packages, or building their own packages from upstream. Note that it currently *is* possible to put a package into updates-testing, it's just not possible to promote it to stable until the alpha freeze is lifted. -- test mailing list test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
