[Libvirt-cim] [RESEND PATCH 0/3] libvirt-cim: Fix provider registration

[John Ferlan]

On 11/05/2013 04:03 AM, Viktor Mihajlovski wrote:
> The following series fixes two issues in the provider registration
> process of the libvirt-cim RPM package.
> First, the RPM scriptlets didn't properly reflect the invocation
> sequence during an RPM upgrade. This is fixed by the first patch.
> Further, the registration using wildcards (*.mof) failed because of
> an inter-MOF depedency. Fixed by the second patch.
> Finally, the class deletion sequence in provider-register.sh was
> prone to failure, resulting in residual entries in the Pegasus
> class repository. Addressed by third patch.
> 
> Note: since the redhat.com mailing lists are bouncing my emails
> I am sending from a different account temporarily until this is
> resolved.
> 
> Viktor Mihajlovski (3):
>   build: Fix incorrect provider registration in upgrade path
>   build: Fix provider registration issues
>   schema: Fix class removal with Pegasus
> 
>  libvirt-cim.spec.in  |  282 ++++++++++++++++++++++++++++++++++++++++----------
>  provider-register.sh |    8 +-
>  2 files changed, 231 insertions(+), 59 deletions(-)
> 

I'm much of an expert in these matters - in fact pre-novice would
summarize my experience with RPM files :-)

Things seem reasonable; however, I'm in a bit of a quandary now as I
cannot get my libvirt-cim environment to work in order to test. This
past Friday I did do a yum update and since that time I cannot seem to
get the libvirt-cim provider and cimserver to talk - quite frustrating.

I was actually hoping to spend this week reviewing and testing
libvirt-cim patches...  Now I'm just trying to figure out why two best
friends won't speak to each other any more :-)

John