Comment 6 for bug 527195

Michael,

I'm not sure what might have happened with the licensing, but AFAIK, those issues were already resolved. Now, at [1] says:

"[This is the first released version of the Lesser GPL. It also counts
 as the successor of the GNU Library Public License, version 2, hence
 the version number 2.1.]"

So I'm presuming that they refer to LGPL-2+, which would include 2.1, maybe? What do you think is the next step here?

On the side of Debian bug #527220, back in the day, Hearbeat (2.x) contained some of the bits that is now found in Pacemaker (We can say there was an split). So, the new package, Pacemaker was created and indeed conflicted with Heartbeat because all those bits weren't removed from the Heartbeat source. (which is the reason of Debian #527220). Anyways, after that, the split was carried on, and Pacemaker source shipped a pacemaker-heartbeat binary package, which contained the compatibility of Pacemaker to use Heartbeat as messaging layer, however, the Heartbeat package was never "updated", and they continued to include files that were found in both packages.

However, after Linbit took over Heartbeat source code (to maintain it), those common bits were removed from Heartbeat (and eventually became Heartbeat 3.x), and the pacemaker package dropped the pacemaker-heartbeat and pacemaker-corosync binary packages. When that happened, the conflict/replaces was added to fix problem when upgrading from a pacemaker version that contained the pacemaker-heartbeat, to the new Pacemaker version that works *with* the heartbeat package. In other words, Pacemaker now works with the heartbeat package (Pacemaker is the cluster resource manager, while Heartbeat is the messaging layer). Obviosly, since these packages are ment to work together, they no longer conflict in any common files.

Hope this helps.

[1]: http://www.gnu.org/licenses/lgpl-2.1.html