Your message dated Tue, 04 Oct 2005 16:02:09 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#298714: fixed in nsmon 2.3e-5
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; 9 Mar 2005 13:59:48 +0000
>From [EMAIL PROTECTED] Wed Mar 09 05:59:48 2005
Return-path: <[EMAIL PROTECTED]>
Received: from c223012.adsl.hansenet.de (localhost.localdomain) [213.39.223.12]
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1D91j2-0000qh-00; Wed, 09 Mar 2005 05:59:48 -0800
Received: from aj by localhost.localdomain with local (Exim 4.44)
id 1D92fS-0006Gr-DB; Wed, 09 Mar 2005 16:00:10 +0100
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
From: Andreas Jochens <[EMAIL PROTECTED]>
Subject: nsmon: FTBFS (amd64/gcc-4.0): array type has incomplete element type
Message-Id: <[EMAIL PROTECTED]>
Date: Wed, 09 Mar 2005 16:00:10 +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=-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: nsmon
Severity: normal
Tags: patch
When building 'nsmon' on amd64 with gcc-4.0,
I get the following error:
make[1]: Entering directory `/nsmon-2.3e'
gcc -Wall -O2 -c nsmon.c
In file included from run_check.h:9,
from nsmon.c:6:
config.h:27: error: array type has incomplete element type
In file included from run_check.h:9,
from nsmon.c:6:
config.h:58:7: warning: no newline at end of file
In file included from nsmon.c:6:
run_check.h:13:7: warning: no newline at end of file
In file included from nsmon.c:7:
ping_test.h:23:7: warning: no newline at end of file
In file included from nsmon.c:9:
port_test.h:15:7: warning: no newline at end of file
nsmon.c:116:3: warning: no newline at end of file
make[1]: *** [nsmon.o] Error 1
make[1]: Leaving directory `/nsmon-2.3e'
make: *** [build-stamp] Error 2
With the attached patch 'nsmon' can be compiled
on amd64 using gcc-4.0.
Regards
Andreas Jochens
diff -urN ../tmp-orig/nsmon-2.3e/config.h ./config.h
--- ../tmp-orig/nsmon-2.3e/config.h 1999-02-15 00:00:00.000000000 +0100
+++ ./config.h 2005-03-09 15:51:41.550886118 +0100
@@ -24,7 +24,7 @@
#define DEFAULT_CONFIG "/etc/nsmon.conf"
#define VERSION "2.3e"
-struct checkhost hosts[20];
+struct checkhost *hosts;
char LOCK_DIR[1024];
int hostnum; // Number of hosts
pid_t mainpid;
@@ -55,4 +55,4 @@
void read_config (/* char *configfile */);
void logit(/* char *s */);
-#endif
\ No newline at end of file
+#endif
---------------------------------------
Received: (at 298714-close) by bugs.debian.org; 4 Oct 2005 23:08:05 +0000
>From [EMAIL PROTECTED] Tue Oct 04 16:08:05 2005
Return-path: <[EMAIL PROTECTED]>
Received: from katie by spohr.debian.org with local (Exim 3.36 1 (Debian))
id 1EMvnV-0003gQ-00; Tue, 04 Oct 2005 16:02:09 -0700
From: Andrew Pollock <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
X-Katie: $Revision: 1.56 $
Subject: Bug#298714: fixed in nsmon 2.3e-5
Message-Id: <[EMAIL PROTECTED]>
Sender: Archive Administrator <[EMAIL PROTECTED]>
Date: Tue, 04 Oct 2005 16:02:09 -0700
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-Level:
X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER
autolearn=no version=2.60-bugs.debian.org_2005_01_02
Source: nsmon
Source-Version: 2.3e-5
We believe that the bug you reported is fixed in the latest version of
nsmon, which is due to be installed in the Debian FTP archive:
nsmon_2.3e-5.dsc
to pool/main/n/nsmon/nsmon_2.3e-5.dsc
nsmon_2.3e-5.tar.gz
to pool/main/n/nsmon/nsmon_2.3e-5.tar.gz
nsmon_2.3e-5_i386.deb
to pool/main/n/nsmon/nsmon_2.3e-5_i386.deb
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Andrew Pollock <[EMAIL PROTECTED]> (supplier of updated nsmon package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [EMAIL PROTECTED])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.7
Date: Wed, 5 Oct 2005 08:47:56 +1000
Source: nsmon
Binary: nsmon
Architecture: source i386
Version: 2.3e-5
Distribution: unstable
Urgency: low
Maintainer: Debian QA Group <[EMAIL PROTECTED]>
Changed-By: Andrew Pollock <[EMAIL PROTECTED]>
Description:
nsmon - intranet/internet server checker
Closes: 298714
Changes:
nsmon (2.3e-5) unstable; urgency=low
.
* QA Group upload orphaning this package
* debian/control: Build-Depend on dpatch
* debian/rules: Add dpatch support
* Added patch from Andreas Jochens to fix FTBFS with gcc-4.0 (closes:
#298714)
* debian/conffiles: removed as it was redundant
* debian/control: rephrased package description synopsis
* debian/copyright: Updated FSF address
* debian/copyright: mentioned location of the full text of the GPL
* debian/changelog: removed Emacs crap from the bottom
Files:
629181ebc77ceaa2c11abfcce6d25cfb 501 net optional nsmon_2.3e-5.dsc
9a0982944d96ddada9fa670fbd1a8b96 21811 net optional nsmon_2.3e-5.tar.gz
097aad5b2a78f75ddefea264307f63fd 16586 net optional nsmon_2.3e-5_i386.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
iD8DBQFDQwb7IblXXKfZFgIRApQHAJ9u4+fIyf7qK6U1oELq3vgS6WeksACeOKX1
gYzmsBRKNyvgl4Ttv4ssVz4=
=zZr5
-----END PGP SIGNATURE-----
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
