<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<!DOCTYPE bugzilla SYSTEM "http://bugs.gentoo.org/bugzilla.dtd">

<bugzilla version="2.22.7"
          urlbase="http://bugs.gentoo.org/"
          maintainer="bugzilla@gentoo.org"
>

    <bug>
          <bug_id>190828</bug_id>
          
          <creation_ts>2007-08-30 22:16 0000</creation_ts>
          <short_desc>sys-fs/evms-2.5.5-r7 rekeyword unstable</short_desc>
          <delta_ts>2007-10-22 14:32:22 0000</delta_ts>
          <reporter_accessible>1</reporter_accessible>
          <cclist_accessible>1</cclist_accessible>
          <classification_id>1</classification_id>
          <classification>Unclassified</classification>
          <product>Gentoo Linux</product>
          <component>Ebuilds</component>
          <version>unspecified</version>
          <rep_platform>All</rep_platform>
          <op_sys>Linux</op_sys>
          <bug_status>RESOLVED</bug_status>
          <resolution>FIXED</resolution>
          
          
          
          <priority>P2</priority>
          <bug_severity>normal</bug_severity>
          <target_milestone>---</target_milestone>
          
          
          
          <everconfirmed>1</everconfirmed>
          <reporter>dev-zero@gentoo.org</reporter>
          <assigned_to>dev-zero@gentoo.org</assigned_to>
          <cc>fmccor@gentoo.org</cc>

      

      
          <long_desc isprivate="0">
            <who>dev-zero@gentoo.org</who>
            <bug_when>2007-08-30 22:16:32 0000</bug_when>
            <thetext>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&apos;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.</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>fmccor@gentoo.org</who>
            <bug_when>2007-08-31 15:20:55 0000</bug_when>
            <thetext>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&apos;t make the advertised test procedure work on either amd64 or on sparc.  Likely I&apos;m missing something obvious, but I am doing exactly what the ebuild suggests.
</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>corsair@gentoo.org</who>
            <bug_when>2007-10-11 11:30:01 0000</bug_when>
            <thetext>added ~ppc64</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>armin76@gentoo.org</who>
            <bug_when>2007-10-22 11:38:23 0000</bug_when>
            <thetext>~ia64 done on -r9, closing.</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>armin76@gentoo.org</who>
            <bug_when>2007-10-22 14:32:22 0000</bug_when>
            <thetext>Closing now</thetext>
          </long_desc>
      
    </bug>

</bugzilla>