Re: problem with python-libvirt (1.2.1-2~bpo70+1) package in wheezy-backports apt source

[Yunqiang Su <wzssyqa@gmail.com>]

On Thu, May 29, 2014 at 10:39 AM, Qiang Guan
<hzguanqiang@corp.netease.com> wrote:
>
>
> Hi Guys,
>
> I noticed libvirt packages in wheezy-backports source are with the following
> version:
>
> python-libvirt 1.2.1-2~bpo70+1: amd64 armel armhf i386 ia64 kfreebsd-amd64
> kfreebsd-i386 mips mipsel powerpc s390 s390x sparc
> libvirt-bin 1.2.4-1~bpo70+1: amd64 armel armhf i386 ia64 mips mipsel powerpc
> s390x
> libvirt-bin 1.2.1-1~bpo70+1: kfreebsd-amd64 kfreebsd-i386 mips s390 sparc
>

Maybe, then, on some architectures, it is still building.

>
> Why don't debian wheezy-backports apt source package python-libvirt with
> version 1.2.4 while libvirt-bin have 1.2.4 version?
>
> It seems that in python-libvirt1.2.1, many set-APIs just like
> ''setBlkioParameters" have bugs which is fixed in 1.2.4 version
> with patch "setPyVirTypedParameter: Copy full field name"(commitid:
> 412c93a7b9111ad15c543e286f23bb5891749c42)
> in libvirt git repository (git://libvirt.org/libvirt-python.git).
>
>
> Best Regards~
> Jackie
>
>



-- 
Yunqiang Su