Bugzilla Bug 178635

All current versions of gammu are broken on 2.6.21 (see
http://blog.cihar.com/archives/2007/04/24/kernel_2_6_21_hits_gammu/). Please 
bump to latest stable 1.11.0 and remove old versions (or set DEPEND on kernel
<2.6.21). Renaming ebuild 1.10.0 and removing src_unpack is enough to version
bump (patches appear to be already applied upstream).

If you use this package, please become its maintainer.
I only maintain it because no one else seem interested.

Sorry, I don't want to maintain it, but I can fix this bug if you want?

Damn. I was hoped you will take gammu and friends under your wing :(.

The new version is now in cvs. I had to patch it though (it had 2 bugs revealed
by the compiler's warnings). 

I will nag the arch teams when the one month probation period will end.

I'll be asking arches to mark 2.6.21 stable within the next few days, would be
great if this issue could be fixed before that time.

Arches, please mark following ebuilds as stable:
  app-mobilephone/gammu-1.11.0
  dev-python/python-gammu-0.20
  app-mobilephone/wammu-0.20 (this one don't even have ~ia64)

ia64 keyword dropped, i don't have the hardware to test and nobody has.

x86 stable, works fine

Created an attachment (id=122898) [edit]
elog file for gammu 1.12.0

Created an attachment (id=122899) [edit]
gammu 1.12.0 ebuild file

Hy Alin,

I would overtake the packages wammu and gammu. But I need an introduction how
to create the ebuild file.

I had tried to create the new ebuild file for version 1.12.0 based on the
ebuild file for the lastet version in the portage. But I got always an linker
error.
So I have attached the both files where you can analyze the error.

Can you please help me to maintance these both packages.

regards
j0inty

(From update of attachment 122899 [edit])
# Copyright 1999-2007 Gentoo Foundation
# Distributed under the terms of the GNU General Public License v2
# $Header: /var/cvsroot/gentoo-x86/app-mobilephone/gammu/gammu-1.12.0.ebuild,v
1.5 2007/06/23 15:22:20 j0inty Exp $
inherit eutils

DESCRIPTION="a fork of the gnokii project, a tool to handle your cellular
phone"
HOMEPAGE="http://www.gammu.org"
SRC_URI="ftp://dl.cihar.com/gammu/releases/${P}.tar.bz2"

LICENSE="GPL-2"
SLOT="0"
KEYWORDS="~amd64 ~ppc ~x86"
IUSE="debug bluetooth irda mysql postgres nls nokiaphones"

RDEPEND="bluetooth? ( net-wireless/bluez-libs )
        mysql? ( virtual/mysql )
        postgres? ( dev-db/postgresql )"
DEPEND="${RDEPEND}
        irda? ( virtual/os-headers )
        sys-devel/autoconf-wrapper
        dev-util/pkgconfig
        dev-util/cmake"

src_unpack() {
        unpack ${A}
}

src_compile() {
        local myconf=""
        use debug && myconf="${myconf} -DCMAKE_BUILD_TYPE=\"Debug\""
        use bluetooth || myconf="${myconf} -DWITH_Bluez=OFF"
        use mysql && myconf="${myconf} -DMYSQL_CROSS_PATH=/usr/lib/mysql/"
        use postgres && myconf="${myconf} -DPOSTGRES_CROSS_PATH=/usr/lib/pgsql"
        use nls && myconf="${myconf} -DGETTEXT_CROSS_PATH=/usr/lib/gettext/"
        use irda || myconf="${myconf} -DWITH_IrDA=OFF"

        ## EXPERIMENTAL USE FLAG
        #use nokiaphones || myconf="${myconf} -DWITH_NOKIA_SUPPORT=OFF"

# Create and change to the build directory. (@see INSTALL file)
        mkdir build 
        cd build
# Call cmake
        cmake .. \
                -DCMAKE_INSTALL_PREFIX=/usr \
                -DENABLE_SHARED=ON \
                ${myconf} || die "configure failed"

        emake || die "make failed"
}

src_install () {
        make DESTDIR="${D}" install || die "install failed"
        mv "${D}/usr/share/doc/${PN}" "${D}/usr/share/doc/${P}"
}

(In reply to comment #11)

Please don't hijack unrelated bugs. The bump has been fixed, as requested in
bug 183323. 

app-mobilephone/gammu-1.11.0 stable on ppc.

dev-python/python-gammu and app-mobilephone/wammu don't have a stable ppc
keyword yet.  As long as no user requests it, we keep it in testing.  So, ppc
done.

This bug's been open for a while now and appears to be blocking the marking of
kernel 2.6.21-r4 stable on amd64. Is there an issue with it on amd64?

Yes.

To clarify - yes, this bug affects amd64. As to why it hasn't been fixed -
maybe no amd64 testers have a gammu compatible phone? Maybe nobody has the
time?

amd64 stable