Comment 4 for bug 1272059

Revision history for this message
Kent Baxley (kentb) wrote :

It was recommended that I try and break out the shared libraries into their own binary packages. libopenwsman1 contains different libraries with different ABI versions in them, so, naming libopenwsman1 to libopenwsman2 didn't seem to be very wise.

In response, I have broken out libopenwsman into the following packages:

libwsman1
libwsman-client2
libwsman-curl-client-transport1

All of the above have a "Replaces" directive for libopenwsman1

and I have also taken the libwsman-server libraries out of the main openwsman package and put them in their own libwsman-server1 package.

I built a new version of openwsman-2.4.3 and put it in here:
https://launchpad.net/~dell-poweredge-team/+archive/sblim-builds/+packages

I also have a build of wsmancli in that ppa that built against the above openwsman release. So far, so good.

Here's how I tested the fix:

1) Installed wsmancli and libopenwsman1 from the main trusty archive and
verified that wsmancli failed to work.

2) Added the above ppa and updated wsmancli from it. I verified that the new
libwsman packages also came in as replacements for libopenwsman1.

3) Tested wsmancli and verified that it no longer dies looking for
missing libraries.

Please have a look at the packages and let me know if anything else needs adjusting. I'll remove my current debdiffs and, if desired, post new ones if everything checks out OK. Thanks.