On Tue, Sep 08, 2015 at 08:30:19PM +0200, Guido Günther wrote:
>On Tue, Sep 08, 2015 at 09:58:12AM +0200, Martin Kletzander wrote:
>[..snip..]
>>No message like that for me. I completes with 2 test failures (namely
>>qemuxml2argvtest and virsh-uriprecedence), but no problem with any
>
>That's caused by:
>
>
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=781232
>
Oh, and I thought that would be fixed by 8f17d0eaae7ee. So it looks
like the libxml2 version there is somewhere between 8eb55d782a2b and
beb7281055db.
>if the maintainer doesn't act before that it will be fixed with my
>libxml2 NMU:
>
>
https://ftp-master.debian.org/deferred.html
>
OK, cool, thanks for the info.
>>html files being generated. And I tried this on both stable and
>>unstable debian installations.
>>
>>Would you mind also trying one patch I proposed upstream? I know it
>>will seem a bit far-fetched, desperate times call for desperate
>>measures, I guess. I'm talking about this one:
>>
>>https://www.redhat.com/archives/libvir-list/2015-September/msg00194.html
>
>Nope, same error. I'll try to have another look later this week.
Thanks, I think we really need to revert your fix in the meantime,
though, as the internal documentation pages are broken:
https://libvirt.org/internals/locking.html
Sure. Ack from me to revert this.
Cheers,
-- Guido