Hi Satheera,
since this was waiting for verification so long the version number used in the ppa was consumed by another (unrelated) update. I think there is no reason to drive all of the rebuild just for this as there is an easier way to do the testing against the version in the ppa as-is.
You will need to force the install of the version from the ppa being 1.3.1-1ubuntu10.15~ppa1
Fortunately I see in your report above that the newer libvirt-bin 1.3.1-1ubuntu10.15 was in use.
So if after adding the ppa you could not just normally apt update&upgrade but then force the version like:
$ apt install libvirt-bin=1.3.1-1ubuntu10.15~ppa1 libvirt0=1.3.1-1ubuntu10.15~ppa1
This would allow you to check from the ppa without any collision with this or other updates.
Hi Satheera,
since this was waiting for verification so long the version number used in the ppa was consumed by another (unrelated) update. I think there is no reason to drive all of the rebuild just for this as there is an easier way to do the testing against the version in the ppa as-is.
You will need to force the install of the version from the ppa being 1.3.1-1ubuntu10 .15~ppa1 bin=1.3. 1-1ubuntu10. 15~ppa1 libvirt0= 1.3.1-1ubuntu10 .15~ppa1
Fortunately I see in your report above that the newer libvirt-bin 1.3.1-1ubuntu10.15 was in use.
So if after adding the ppa you could not just normally apt update&upgrade but then force the version like:
$ apt install libvirt-
This would allow you to check from the ppa without any collision with this or other updates.