Your message dated Mon, 25 Apr 2005 16:32:42 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#306324: fixed in quagga 0.98.3-3
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; 25 Apr 2005 19:04:49 +0000
>From [EMAIL PROTECTED] Mon Apr 25 12:04:48 2005
Return-path: <[EMAIL PROTECTED]>
Received: from head.linpro.no [80.232.36.1] 
        by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
        id 1DQ8sy-0006Zm-00; Mon, 25 Apr 2005 12:04:48 -0700
Received: from pride.fud.no ([213.145.167.26])
        by head.linpro.no with asmtp (Exim 4.14 #1 (Debian))
        id 1DQ8st-0005y4-WB; Mon, 25 Apr 2005 21:04:44 +0200
Subject: Postinst never finishes in 0.98.3-2
From: Tore Anderson <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Content-Type: text/plain
Date: Mon, 25 Apr 2005 21:04:43 +0200
Message-Id: <[EMAIL PROTECTED]>
Mime-Version: 1.0
X-Mailer: Evolution 2.2.2 
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scanner: exiscan for exim4 (http://duncanthrax.net/exiscan/) 
*1DQ8st-0005y4-WB*xUDFne8gruQ*
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: quagga
Severity: grave
Tags: sid

  Since the addition of the confmodule inclusion in the postinst, it
 never finishes after having started the Quagga daemons (I run zebra,
 bgpd, and ospfd).  This is due to misdesign in Debconf that's unlikely
 to be fixed soon, see #50595.

  There's two ways you can fix this:

  1) Explicitly call db_stop in the postinst.
  2) Stop including confmodule, it serves no purpose anyway.
     (Lintian should be ignored, it's obviously wrong here.)

  I've set the severity to RC as it's the only change since 0.98.3-1,
 and -2 doesn't change anything except adding this bug, so there's as
 far as I can see no good reason to let it replace 0.98.3-1 in Sarge
 (but one very good reason to stop it from doing so;  preventing Sarge
 from including this very bug).

Kind regards,
-- 
Tore Anderson


---------------------------------------
Received: (at 306324-close) by bugs.debian.org; 25 Apr 2005 20:51:32 +0000
>From [EMAIL PROTECTED] Mon Apr 25 13:51:32 2005
Return-path: <[EMAIL PROTECTED]>
Received: from newraff.debian.org [208.185.25.31] (mail)
        by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
        id 1DQAYG-0003WP-00; Mon, 25 Apr 2005 13:51:32 -0700
Received: from katie by newraff.debian.org with local (Exim 3.35 1 (Debian))
        id 1DQAG2-00067W-00; Mon, 25 Apr 2005 16:32:42 -0400
From: Christian Hammers <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
X-Katie: $Revision: 1.55 $
Subject: Bug#306324: fixed in quagga 0.98.3-3
Message-Id: <[EMAIL PROTECTED]>
Sender: Archive Administrator <[EMAIL PROTECTED]>
Date: Mon, 25 Apr 2005 16:32:42 -0400
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: 

Source: quagga
Source-Version: 0.98.3-3

We believe that the bug you reported is fixed in the latest version of
quagga, which is due to be installed in the Debian FTP archive:

quagga-doc_0.98.3-3_all.deb
  to pool/main/q/quagga/quagga-doc_0.98.3-3_all.deb
quagga_0.98.3-3.diff.gz
  to pool/main/q/quagga/quagga_0.98.3-3.diff.gz
quagga_0.98.3-3.dsc
  to pool/main/q/quagga/quagga_0.98.3-3.dsc
quagga_0.98.3-3_i386.deb
  to pool/main/q/quagga/quagga_0.98.3-3_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.
Christian Hammers <[EMAIL PROTECTED]> (supplier of updated quagga 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: Mon, 25 Apr 2005 21:55:58 +0200
Source: quagga
Binary: quagga quagga-doc
Architecture: source i386 all
Version: 0.98.3-3
Distribution: unstable
Urgency: medium
Maintainer: Christian Hammers <[EMAIL PROTECTED]>
Changed-By: Christian Hammers <[EMAIL PROTECTED]>
Description: 
 quagga     - unoff. successor of the Zebra BGP/OSPF/RIP routing daemon
 quagga-doc - documentation files for quagga
Closes: 306324
Changes: 
 quagga (0.98.3-3) unstable; urgency=medium
 .
   * Adding the debconf module due to a lintian suggestion is a very
     bad idea if no db_stop is called as the script hangs then (thanks
     to Tore Anderson for reporting). Closes: #306324
Files: 
 932a8363d60f3862b0291ecfaa93622b 704 net optional quagga_0.98.3-3.dsc
 0e0f1da52f46461673956a539f41e44e 31077 net optional quagga_0.98.3-3.diff.gz
 46ffcc5ea17001d86185bec3a58733b9 482350 net optional 
quagga-doc_0.98.3-3_all.deb
 3cd1e2f1f25ba25dd3d2e19561a83a62 1229410 net optional quagga_0.98.3-3_i386.deb

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

iEYEARECAAYFAkJtT8kACgkQkR9K5oahGOZvNQCfdq04tefw3ngVtcxQqapmQpuI
TT0AoIQPi2uXJHzN/kOyZnJQcIhADePz
=a2NC
-----END PGP SIGNATURE-----


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

Reply via email to