Your message dated Sat, 21 May 2005 14:18:06 +0200
with message-id <[EMAIL PROTECTED]>
and subject line this is no longer the case
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--------------------------------------
Received: (at submit) by bugs.debian.org; 6 Apr 2005 11:21:45 +0000
>From [EMAIL PROTECTED] Wed Apr 06 04:21:45 2005
Return-path: <[EMAIL PROTECTED]>
Received: from (mulder.hem.za.org) [84.217.19.97] 
        by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
        id 1DJ8bR-0003AJ-00; Wed, 06 Apr 2005 04:21:45 -0700
Received: from skinner.hem.za.org ([fec0::202:44ff:fe1d:d021])
        by mulder.hem.za.org with esmtp (Exim 4.50)
        id 1DJ8bP-00035l-Gj
        for [EMAIL PROTECTED]; Wed, 06 Apr 2005 13:21:43 +0200
Received: from mikael by skinner.hem.za.org with local (Exim 4.50)
        id 1DJ8bP-0008VE-8O
        for [EMAIL PROTECTED]; Wed, 06 Apr 2005 13:21:43 +0200
Date: Wed, 6 Apr 2005 13:21:42 +0200
From: Mikael Magnusson <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: asterisk: Depends on zaptel.h which is in a tar-ball
Message-ID: <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
X-Reportbug-Version: 3.8
User-Agent: Mutt/1.5.6+20040907i
Sender: Mikael Magnusson <[EMAIL PROTECTED]>
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 
        (1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE 
        autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level: 

Package: asterisk
Version: 1:1.0.7.dfsg.1-2
Severity: important

When building from the source package I noticed that it didn't build
chan_zap.so, app_flash.so, app_meetme.so, app_zapbarge.so,
app_zapras.so and app_zapscan.so.

It's caused by the fact that /usr/src/modules/zaptel/zaptel.h is
distributed in zaptel.tar.bz2, and I hadn't extracted that archive.

There doesn't seem to be a problem with the current binary packages,
but I think it will be if/when the autobuilders build the next asterisk
version.

/Mikael Magnusson

-- System Information:
Debian Release: 3.1
  APT prefers testing
  APT policy: (950, 'testing'), (900, 'testing'), (150, 'unstable'), (100, 
'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.10-1-k7
Locale: LANG=sv_SE.UTF-8, LC_CTYPE=sv_SE.UTF-8 (charmap=UTF-8)

Versions of packages asterisk depends on:
pn  asterisk-sounds                          Not found.
ii  libasound2            1.0.8-3            ALSA library
ii  libc6                 2.3.2.ds1-20       GNU C Library: Shared libraries an
ii  libedit2              2.9.cvs.20040827-1 BSD editline and history libraries
ii  libexpat1             1.95.8-1           XML parsing C library - runtime li
ii  libgsm1               1.0.10-13          Shared libraries for GSM speech co
ii  libncurses5           5.4-4              Shared libraries for terminal hand
ii  libopenh323-1.12.2    1.12.2-4           H.323 aka VoIP library
ii  libpq3                7.4.7-2            PostgreSQL C client library
ii  libpri1               1.0.7-1            Primary Rate ISDN specification li
ii  libpt-1.5.2           1.5.2-4            Portable Windows Library
ii  libssl0.9.7           0.9.7e-3           SSL shared libraries
ii  libtonezone1          1:1.0.7-3          tonezone library (runtime)
ii  unixodbc              2.2.4-11           ODBC tools libraries
ii  zlib1g                1:1.2.2-3          compression library - runtime

---------------------------------------
Received: (at 303371-done) by bugs.debian.org; 21 May 2005 12:18:11 +0000
>From [EMAIL PROTECTED] Sat May 21 05:18:11 2005
Return-path: <[EMAIL PROTECTED]>
Received: from nyx.verfaction.de (mx.verfaction.de) [212.9.161.72] (Debian-exim)
        by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
        id 1DZSvi-0004KL-00; Sat, 21 May 2005 05:18:11 -0700
Received: from ontheroad.with.verfaction.de ([3ffe:400:d00:5005::cafe])
        by mx.verfaction.de with esmtpsa (TLS-1.0:RSA_ARCFOUR_MD5:16)
        (Exim 4.50)
        id 1DZSvh-0000mD-IY
        for [EMAIL PROTECTED]; Sat, 21 May 2005 14:18:09 +0200
From: Kilian Krause <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Content-Type: multipart/signed; micalg=pgp-sha1; 
protocol="application/pgp-signature"; boundary="=-xqjM5Ksq0tXoqTsNrwVc"
Date: Sat, 21 May 2005 14:18:06 +0200
Message-Id: <[EMAIL PROTECTED]>
Mime-Version: 1.0
X-Mailer: Evolution 2.2.2 
X-SA-Exim-Connect-IP: 3ffe:400:d00:5005::cafe
X-SA-Exim-Mail-From: [EMAIL PROTECTED]
Subject: this is no longer the case
X-SA-Exim-Version: 4.2 (built Thu, 03 Mar 2005 10:44:12 +0100)
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 
        (1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-3.0 required=4.0 tests=BAYES_00 autolearn=no 
        version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level: 


--=-xqjM5Ksq0tXoqTsNrwVc
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

Hi,

new zaptel-source has fixed this problem for quite some time already.
Thus the zaptel.h is now in /usr/include where it is found with no
hazzle.

--=20
Best regards,
 Kilian

--=-xqjM5Ksq0tXoqTsNrwVc
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)

iD8DBQBCjyb+vdkzt4X+wX8RAuONAJ4pMC5uC0yqsppEPh0Tw7PQzZs7yACeNS84
YK4Iu0cvBBSOi431FDhYT0M=
=N3wK
-----END PGP SIGNATURE-----

--=-xqjM5Ksq0tXoqTsNrwVc--


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to