Your message dated Fri, 3 Jun 2005 03:03:38 -0400
with message-id <[EMAIL PROTECTED]>
and subject line [Pkg-nagios-devel] Bug#311705: nagios-mysql: incorrect path in 
README.mysql
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; 2 Jun 2005 20:21:16 +0000
>From [EMAIL PROTECTED] Thu Jun 02 13:21:16 2005
Return-path: <[EMAIL PROTECTED]>
Received: from faye.voxel.net [69.9.164.210] (900c66047fa2ae7ffe486b8d9e75629e)
        by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
        id 1DdwBo-0005zT-00; Thu, 02 Jun 2005 13:21:16 -0700
Received: from jack.dev.in.athenacr.com (unknown [66.150.84.1])
        by faye.voxel.net (Postfix) with ESMTP id 04A703726D
        for <[EMAIL PROTECTED]>; Thu,  2 Jun 2005 16:21:14 -0400 (EDT)
Subject: nagios-mysql: incorrect path in README.mysql
From: Andres Salomon <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Content-Type: text/plain
Date: Thu, 02 Jun 2005 16:21:14 -0400
Message-Id: <[EMAIL PROTECTED]>
Mime-Version: 1.0
X-Mailer: Evolution 2.0.2 
Content-Transfer-Encoding: 7bit
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: nagios-mysql
Version: 1.3-cvs.20050402-2
Severity: normal

Hi,

README.mysql contains the following comment:

"
3)

Then you want the cgi-script and the init.d script to correctly
know the status of nagios. To do this you will need something like the
check_nagios_db file from /usr/doc/nagios-common/. "


/usr/doc/nagios-common/check_nagios_db doesn't actually exist.  What
does seem to exist is /usr/share/doc/nagios-common/check_nagios_db.  The
documentation should probably be updated to reflect that.





---------------------------------------
Received: (at 311705-done) by bugs.debian.org; 3 Jun 2005 07:04:18 +0000
>From [EMAIL PROTECTED] Fri Jun 03 00:04:18 2005
Return-path: <[EMAIL PROTECTED]>
Received: from dsl092-235-113.phl1.dsl.speakeasy.net (sativa.seanius.net) 
[66.92.235.113] 
        by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
        id 1De6E5-0005tL-00; Fri, 03 Jun 2005 00:04:17 -0700
Received: by sativa.seanius.net (Postfix, from userid 1000)
        id 4715715846; Fri,  3 Jun 2005 03:03:38 -0400 (EDT)
Date: Fri, 3 Jun 2005 03:03:38 -0400
From: sean finney <[EMAIL PROTECTED]>
To: Andres Salomon <[EMAIL PROTECTED]>, [EMAIL PROTECTED]
Subject: Re: [Pkg-nagios-devel] Bug#311705: nagios-mysql: incorrect path in 
README.mysql
Message-ID: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
        protocol="application/pgp-signature"; boundary="8t9RHnE3ZwKMSgU+"
Content-Disposition: inline
In-Reply-To: <[EMAIL PROTECTED]>
User-Agent: Mutt/1.5.5.1+cvs20040105i
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=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER 
        autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level: 


--8t9RHnE3ZwKMSgU+
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Thu, Jun 02, 2005 at 04:21:14PM -0400, Andres Salomon wrote:
> /usr/doc/nagios-common/check_nagios_db doesn't actually exist.  What
> does seem to exist is /usr/share/doc/nagios-common/check_nagios_db.  The
> documentation should probably be updated to reflect that.

this was previously reported, and fixed in an upload i did this morning :)


        sean

--=20

--8t9RHnE3ZwKMSgU+
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

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

iD8DBQFCoADKynjLPm522B0RApPkAJ9n+jAmKCvk0mFqDQKH2DswbYWrrACdF6y5
wSZjOQLaksGtrb0dZ+OKxC4=
=nrlh
-----END PGP SIGNATURE-----

--8t9RHnE3ZwKMSgU+--


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

Reply via email to