Bugzilla Bug 190828

Hi there.

Support for hearbeat-1/-2 has been added due to user request (support for
heartbeat-1 was already active automagically, now controlled by the hb use
flag).

Your archs don't have unstable keywords for =sys-cluster/heartbeat-1* and
=sys-cluster/heartbeat-2*.

You have three options:
- Mask both hb and hb2 use flags for your arch and re-add your unstable keyword
to sys-fs/evms
- Mask only the hb use flag and test heartbeat-2 and add your unstable keyword
to both heartbeat-2 and evms
- Mark both heartbeat versions and evms unstable for your arch

Thanks in advance for your work.

For tests regarding evms, please read the ebuild.

If on sparc or on amd64 I follow the procedure given to set up a loopback
device, I always get this:
=================
 * Disabling sandbox for:
 *  - /dev/loop/0
 *  - /dev/evms
 *  - /var/lock/evms-engine
Checking for required tools:
     evms: OK
     evms_clean: OK
     dmsetup: OK
     blockdev: OK
     stat: OK
     seq_dd: OK
     wget: OK
Checking existance of disks:
     /dev/loop/0: Not found
Error: Cannot access all specified disks.
=============================

On sparc, I get the same for evmv-2.5.5-r5, which is marked stable, so I am
giving evms-2.5.5-r7 a ~sparc keyword.  However, I note that this is not
tested.
(I did not check a stable version of evms on amd64, but I have no reason to
believe it would run with FEATURES=test using the loopback device).

In summary:  heartbeat-1.2.5-r1, heartbeat-2.0.8, ipvsadm-1.24, and
evms-2.5.5-r7 have all been marked ~sparc.

However, please advise on testing:  I can't make the advertised test procedure
work on either amd64 or on sparc.  Likely I'm missing something obvious, but I
am doing exactly what the ebuild suggests.

added ~ppc64

~ia64 done on -r9, closing.

Closing now