<?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>86086</bug_id>
          
          <creation_ts>2005-03-20 19:24 0000</creation_ts>
          <short_desc>Kdissert ~amd64 marking request</short_desc>
          <delta_ts>2005-03-21 00:51:51 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>AMD64</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>will.briggs@bigpond.com</reporter>
          <assigned_to>amd64@gentoo.org</assigned_to>
          <cc>kde@gentoo.org</cc>

      

      
          <long_desc isprivate="0">
            <who>will.briggs@bigpond.com</who>
            <bug_when>2005-03-20 19:24:40 0000</bug_when>
            <thetext>I wanted to emerge kdissert on my amd64 system.  There are no amd64 keywords (stable or unstable) in the kdissert ebuild so I copied the kdissert part of the portage tree to my my local portage overlay and added the keyword to the ebuild (kdissert-0.3.6) (see additional info).

The emerge worked and some cursory testing seems to indicate that kdissert operates correctly on this architecture.

Is there any reason why ~amd64 keyword cannot be added to the ebuild and therefore have a wider testing on this platform amongs the user community?

Reproducible: Always
Steps to Reproduce:
1.Add ~amd64 keyword to ebuild in portage overlay
2.emerge kdissert

Actual Results:  
Kdissert emerges and seems to operate well

Expected Results:  
Kdissert emerges and seems to operate well

# Copyright 1999-2005 Gentoo Foundation
# Distributed under the terms of the GNU General Public License v2
# $Header: /var/cvsroot/gentoo-x86/kde-misc/kdissert/kdissert-0.3.6.ebuild,v 1.1
2005/02/28 23:09:30 carlo Exp $

inherit kde

MY_P=${P/_/-}
S=${WORKDIR}/${MY_P}

DESCRIPTION=&quot;KDissert - a mindmapping-like tool&quot;
HOMEPAGE=&quot;http://www.freehackers.org/~tnagy/kdissert/index.html&quot;
#SRC_URI=&quot;http://www.freehackers.org/~tnagy/kdissert/${MY_P}.tar.bz2&quot;
SRC_URI=&quot;http://www.kde-apps.org/content/files/12725-${MY_P}.tar.bz2&quot;

SLOT=&quot;0&quot;
LICENSE=&quot;GPL-2&quot;
KEYWORDS=&quot;~x86 ~sparci ~amd64&quot;
IUSE=&quot;&quot;

DEPEND=&quot;dev-util/scons&quot;
need-kde 3.2

# rotten Makefile stuff, can&apos;t use kde.eclass
src_compile() {
        ./configure --prefix=&quot;${D}/usr&quot; --kdeincludes=&quot;$(kde-config
--prefix)/include&quot;  || configure failed
        emake || emake failed
}

src_install() {
        einstall || einstall failed
}</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>chriswhite@gentoo.org</who>
            <bug_when>2005-03-21 00:24:57 0000</bug_when>
            <thetext>~amd64 marking request for kdissert.

amd64 re-assignment
kde herd cc&apos;ed so they&apos;re aware of the marking request.</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>cryos@gentoo.org</who>
            <bug_when>2005-03-21 00:51:51 0000</bug_when>
            <thetext>Please see http://www.gentoo.org/proj/en/base/amd64/howtos/index.xml?part=1&amp;chap=2 for details on filing keyword bugs, there is no need to include ebuilds etc, but the ebuild category and version does help.

I have tested this and marked it ~amd64 - kde-misc/kdissert-0.3.6</thetext>
          </long_desc>
      
    </bug>

</bugzilla>