Your message dated Thu, 03 Feb 2005 02:12:48 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Fixed in 1.0.2-2
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; 8 Aug 2004 20:13:41 +0000
>From [EMAIL PROTECTED] Sun Aug 08 13:13:41 2004
Return-path: <[EMAIL PROTECTED]>
Received: from passoa.byte.nl [217.119.229.6]
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1Btu32-0007x4-00; Sun, 08 Aug 2004 13:13:41 -0700
Received: from kahlua (kahlua.internal [10.1.1.5])
by passoa.byte.nl (Postfix) with ESMTP id 4B69831404B;
Sun, 8 Aug 2004 22:13:09 +0200 (CEST)
Received: by kahlua (Postfix, from userid 500)
id 46E1A9FB6D; Sun, 8 Aug 2004 22:13:08 +0200 (CEST)
Content-Type: multipart/mixed; boundary="===============1656519332=="
MIME-Version: 1.0
From: Allard Hoeve <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: zaptel-source: fails to configure correctly when using make-kpkg
X-Mailer: reportbug 2.62
Date: Sun, 08 Aug 2004 22:13:08 +0200
Message-Id: <[EMAIL PROTECTED]>
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25
(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_2004_03_25
X-Spam-Level:
This is a multi-part MIME message sent by reportbug.
--===============1656519332==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Package: zaptel-source
Version: 1:0.8.1-1
Severity: normal
Tags: patch
Hello Matt,
I seem to have a problem compiling the zaptel-source package using make-kpkg.
Attached is a patch that removes some
problematic code from debian/rules. The patch seems to resolve the issue for me.
The command I run from the kernel sources is:
[EMAIL PROTECTED] linux-2.4.27]$ make-kpkg --rootcmd=fakeroot -us -uc
--revision=corona.1 modules
The output I get is:
> for module in /usr/src/modules/zaptel ; do \
> if test -d $module; then \
> (cd $module; \
> if ./debian/rules KVERS="2.4.27"
> KSRC="/usr/src/corona/linux-2.4.27" \
> [snip!]
> read ans; \
> fi; \
> ); \
> fi; \
> done
> make[1]: Entering directory `/usr/src/modules/zaptel'
> /usr/bin/make -w debian/rules clean
> make[2]: Entering directory `/usr/src/modules/zaptel'
> make[2]: Nothing to be done for `debian/rules'.
> rm -f torisatool makefw tor2fw.h fxstest ztmonitor ztspeed
> [snip, remove files]
> rm -f core
> make[2]: Leaving directory `/usr/src/modules/zaptel'
> INSTALL_PROGRAM += -s
BUG HERE: ^^^^^^^^^^^^^^^^^^^
> make[1]: INSTALL_PROGRAM: Command not found
> make[1]: *** [kdist_clean] Error 127
> make[1]: Leaving directory `/usr/src/modules/zaptel'
> Module /usr/src/modules/zaptel failed.
> Perhaps /usr/src/modules/zaptel does not understand --rootcmd?
> If you see messages that indicate that it is not
> in fact being built as root, please file a bug
> against /usr/src/modules/zaptel.
> Hit return to Continue?
The easiest way to get around the bug is to remove the INSTALL_PROGRAM
definition, which doesn't seem to do anything. I'm
not sure if it is a correct fix, probably not :)
Regards,
Allard Hoeve
-- System Information:
Debian Release: testing/unstable
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.4.20
Locale: LANG=C, LC_CTYPE=C
-- no debconf information
--===============1656519332==
Content-Type: text/x-makefile; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="debian.zaptel.patch"
--- debian/rules.old 2004-02-12 00:29:57.000000000 +0100
+++ debian/rules 2004-08-08 22:03:04.000000000 +0200
@@ -101,9 +101,6 @@
ifneq (,$(findstring debug,$(DEB_BUILD_OPTIONS)))
CFLAGS += -g
endif
-ifeq (,$(findstring nostrip,$(DEB_BUILD_OPTIONS)))
- INSTALL_PROGRAM += -s
-endif
configure: configure-stamp
configure-stamp:
--===============1656519332==--
---------------------------------------
Received: (at 264427-done) by bugs.debian.org; 3 Feb 2005 07:12:27 +0000
>From [EMAIL PROTECTED] Wed Feb 02 23:12:27 2005
Return-path: <[EMAIL PROTECTED]>
Received: from (kerrigan) [63.245.86.104]
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1CwbAA-0005lf-00; Wed, 02 Feb 2005 23:12:27 -0800
Received: from santiago by kerrigan with local (Exim 4.34)
id 1CwbAX-0000Mz-CB
for [EMAIL PROTECTED]; Thu, 03 Feb 2005 02:12:49 -0500
Subject: Fixed in 1.0.2-2
From: Santiago Ruano =?ISO-8859-1?Q?Rinc=F3n?= <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Content-Type: multipart/signed; micalg=pgp-sha1;
protocol="application/pgp-signature"; boundary="=-IKkagWA+sWXSntmlrHne"
Date: Thu, 03 Feb 2005 02:12:48 -0500
Message-Id: <[EMAIL PROTECTED]>
Mime-Version: 1.0
X-Mailer: Evolution 2.0.3
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=-2.0 required=4.0 tests=BAYES_01 autolearn=no
version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level:
--=-IKkagWA+sWXSntmlrHne
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable
I remove the <TAB> in the 1.0.2-2 version.=20
In a few days, I hope to upload the new upstream version
--=-IKkagWA+sWXSntmlrHne
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: Esta parte del mensaje =?ISO-8859-1?Q?est=E1?= firmada
digitalmente
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
iD8DBQBCAc7vQUuEI2/szeARAtVDAJwLe/DyUBBivUgtjsQ4937tY0dSlQCfVv0Z
xpTB4NQ0i2d/Rx2CR93hz+g=
=hdPR
-----END PGP SIGNATURE-----
--=-IKkagWA+sWXSntmlrHne--
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
