Bug#225765: marked as done (varmon doesn't work with devfs)
Your message dated Tue, 17 Aug 2004 07:32:16 -0400
with message-id <E1Bx2CO-0006NG-00@newraff.debian.org>
and subject line Bug#225765: fixed in varmon 1.0.2-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; 1 Jan 2004 16:48:44 +0000
>From dezwart@froob.net Thu Jan 01 10:48:43 2004
Return-path: <dezwart@froob.net>
Received: from mail012.syd.optusnet.com.au [211.29.132.66]
by master.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1Ac5LP-0002WZ-00; Thu, 01 Jan 2004 10:06:43 -0600
Received: from tropism.intranet.froob.net (c211-30-33-252.mirnd1.nsw.optusnet.com.au [211.30.33.252])
by mail012.syd.optusnet.com.au (8.11.6p2/8.11.6) with ESMTP id i01G6fo02516
for <submit@bugs.debian.org>; Fri, 2 Jan 2004 03:06:41 +1100
Received: from tropism.intranet.froob.net (smmsp@localhost [127.0.0.1])
by tropism.intranet.froob.net (8.12.3/8.12.3/Debian-6.6) with ESMTP id i01G6Yi4000538;
Fri, 2 Jan 2004 03:06:37 +1100
Received: (from dezwart@localhost)
by tropism.intranet.froob.net (8.12.3/8.12.3/Debian-6.6) id i01EBIiT020018;
Fri, 2 Jan 2004 01:11:18 +1100
Message-Id: <200401011411.i01EBIiT020018@tropism.intranet.froob.net>
From: Pete de Zwart <dezwart@froob.net>
To: Debian Bug Tracking System <submit@bugs.debian.org>
Subject: varmon doesn't work with devfs
X-Mailer: reportbug 1.50
Date: Fri, 02 Jan 2004 01:11:18 +1100
Delivered-To: submit@bugs.debian.org
X-Spam-Checker-Version: SpamAssassin
2.60-master.debian.org_2003_11_25-bugs.debian.org_2003_12_29
(1.212-2003-09-23-exp) on master.debian.org
X-Spam-Status: No, hits=-5.0 required=4.0 tests=HAS_PACKAGE autolearn=no
version=2.60-master.debian.org_2003_11_25-bugs.debian.org_2003_12_29
X-Spam-Level:
Package: varmon
Version: 1.0.2-1
Severity: important
varmon doesn't work with devfs as it attempts to open a device name that
doesn't exist. Here is a munged snipped of output with strace info:
Scanning for VA safety backplane.
open("/dev/rd/c0d0", O_RDWR|O_NONBLOCK) = -1 ENOENT (No such file or directory)
Please wait a few moments...Unable to open device (No such file or directory)
Once the symlink is made, varmon is happy and works.
However, varmon should open /dev/rd/disc0/disc rather then /dev/rd/c0d0
Regards,
Pete de Zwart.
-- System Information
Debian Release: 3.0
Architecture: i386
Kernel: Linux tropism 2.4.23 #1 SMP Sun Nov 30 11:03:49 EST 2003 i686
Locale: LANG=C, LC_CTYPE=C
Versions of packages varmon depends on:
ii libc6 2.2.5-11.5 GNU C Library: Shared libraries an
ii libncurses5 5.2.20020112a-7 Shared libraries for terminal hand
---------------------------------------
Received: (at 225765-close) by bugs.debian.org; 17 Aug 2004 11:34:52 +0000
>From katie@ftp-master.debian.org Tue Aug 17 04:34:52 2004
Return-path: <katie@ftp-master.debian.org>
Received: from newraff.debian.org [208.185.25.31] (mail)
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1Bx2Eu-0005co-00; Tue, 17 Aug 2004 04:34:52 -0700
Received: from katie by newraff.debian.org with local (Exim 3.35 1 (Debian))
id 1Bx2CO-0006NG-00; Tue, 17 Aug 2004 07:32:16 -0400
From: Julien Danjou <acid@debian.org>
To: 225765-close@bugs.debian.org
X-Katie: $Revision: 1.51 $
Subject: Bug#225765: fixed in varmon 1.0.2-5
Message-Id: <E1Bx2CO-0006NG-00@newraff.debian.org>
Sender: Archive Administrator <katie@ftp-master.debian.org>
Date: Tue, 17 Aug 2004 07:32:16 -0400
Delivered-To: 225765-close@bugs.debian.org
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=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER
autolearn=no version=2.60-bugs.debian.org_2004_03_25
X-Spam-Level:
X-CrossAssassin-Score: 2
Source: varmon
Source-Version: 1.0.2-5
We believe that the bug you reported is fixed in the latest version of
varmon, which is due to be installed in the Debian FTP archive:
varmon_1.0.2-5.diff.gz
to pool/main/v/varmon/varmon_1.0.2-5.diff.gz
varmon_1.0.2-5.dsc
to pool/main/v/varmon/varmon_1.0.2-5.dsc
varmon_1.0.2-5_i386.deb
to pool/main/v/varmon/varmon_1.0.2-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 225765@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Julien Danjou <acid@debian.org> (supplier of updated varmon 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 ftpmaster@debian.org)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.7
Date: Tue, 17 Aug 2004 13:09:13 +0200
Source: varmon
Binary: varmon
Architecture: source i386
Version: 1.0.2-5
Distribution: unstable
Urgency: low
Maintainer: Julien Danjou <acid@debian.org>
Changed-By: Julien Danjou <acid@debian.org>
Description:
varmon - VA RAID monitor
Closes: 220093 225765 233663
Changes:
varmon (1.0.2-5) unstable; urgency=low
.
* New Maintainer (Closes: #233663)
* Remove bugs:// (Closes: #220093)
* Remove Origin
* Patch it for devfs (Closes: #225765)
* Clean debian/rules
* Bump standards to 3.6.1.0
Files:
a0e76235f5f13ab90796c8b0aea49de7 570 admin extra varmon_1.0.2-5.dsc
9c209c301ccc5d342b78691fe29f00eb 2545 admin extra varmon_1.0.2-5.diff.gz
659ebfe2d5eb7e639c5f405d820eb014 478790 admin extra varmon_1.0.2-5_i386.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)
iD8DBQFBIeeppGK1HsL+5c0RAll2AJsEUqhw2k8y16H5YyT0w8xumS5VGgCeOaU8
agpyprwkvlAcJoQQlKaSHLs=
=LS8T
-----END PGP SIGNATURE-----
Reply to: