Hi, On Sat, Aug 22, 2015 at 02:51:46PM +0100, Adam D. Barratt wrote: > On Wed, 2015-08-19 at 18:37 +0200, Guido Günther wrote: > > Hi, > > On Wed, Aug 19, 2015 at 04:49:56PM +0100, Adam D. Barratt wrote: > > > Control: tags -1 + moreinfo > > > > Thanks for looking into this so quickly. > > > > > > > > On Wed, 2015-08-19 at 13:22 +0200, Guido Günther wrote: > > > > the I'd like to update libvirt in unstable to fix the broken AppArmor > > > > > > I assume "stable" :-) > > > > > > > support, a crash during live migration and a error handling problem > > > > leading lots of users into the wrong direction. The debdiff is attached > > > > and all bugs are already fixed in either sid or experimental (due to the > > > > g++ transition). > > > > > > I have to admit that I'd really prefer that to be "already fixed in > > > sid". I'm not sure where libvirt is in the transition pile though. > > > > How would I find out? Libvirt is C but there's very likely C++ in the > > dependency graph. > > As long as there's no C++ code in libvirt itself and it does not expose > any C++ artefacts in its public ABI, uploading it to unstable now should > be fine.
There's no C++ involved so uploaded now... > > > > > We also have to disable the test suite due to a libxml2 bug. > > > > > > Ewww. > > > > Yeah, that's bad. > > I assume simply disabling some tests isn't a useful or viable option? I'd rather put the time into fixing libxml2. While it's possible to skip the affected tests it would introduce more changes in libvirt since we'd need to swith to dh_autoreconf when changing makefiles to skip the tests. I'd rather reenable the tests once libxml2 is fixed (since the libxml2 but also leads to some user visible regressions visible in libvirt) Cheers, -- Guido > > > > > > > + * [be70aec] Fix crash on live migration > > > + this supplements 07dbec0a64783f644854a22aa0355720f0328d17. > > > + Thanks to Eckebrecht von Pappenheim (Closes: #7788171) > > > > > > ITYM #788171. However, the metadata for that bug suggests it's not > > > currently fixed in either experimental or unstable. > > > > Missing bug hygiene on my end. The patch was in fact a cherry-pick from > > a newer version and I just checked that it's still fixed in 1.2.18. > > Ah, thanks. > > Regards, > > Adam >
