On Fri, Nov 22, 2013 at 12:08:46PM -0700, Eric Blake wrote:
FYI I ran 'autobuild.sh' to validate the full RPM builds here.
All right, looks like we're nearly ready to pull the trigger then :)
So here's what I propose changing vs my patch
diff --git a/configure.ac b/configure.ac
index
On 11/25/2013 08:09 AM, Daniel P. Berrange wrote:
On Fri, Nov 22, 2013 at 12:08:46PM -0700, Eric Blake wrote:
FYI I ran 'autobuild.sh' to validate the full RPM builds here.
All right, looks like we're nearly ready to pull the trigger then :)
So here's what I propose changing vs my patch
On 11/22/2013 09:59 AM, Daniel P. Berrange wrote:
From: Daniel P. Berrange berra...@redhat.com
The python binding now lives in
http://libvirt.org/git/libvirt-python.git
that repo also provides an RPM which is upgrade compatible
with the old libvirt-python sub-RPM.
Signed-off-by:
On Fri, Nov 22, 2013 at 10:57:00AM -0700, Eric Blake wrote:
On 11/22/2013 09:59 AM, Daniel P. Berrange wrote:
run.in |9 -
and this (hmm, do we need a ./run counterpart added to libvirt-python to
make it easy to import a built but uninstalled
On 11/22/2013 11:19 AM, Daniel P. Berrange wrote:
-/python/libvirt.py
-/python/libvirt_lxc.py
-/python/libvirt_qemu.py
Oddly enough, removing these lines will mean that someone with an
incremental tree that likes to switch branches between master and any
earlier branch (say v1.0.5-maint)
