Your message dated Sat, 4 Feb 2006 16:38:33 +0100 with message-id <[EMAIL PROTECTED]> and subject line [EMAIL PROTECTED]: Bug#350630: fixed] 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)
--- Begin Message --->From [EMAIL PROTECTED] Wed Oct 29 09:00:17 2003 Received: (at submit) by bugs.debian.org; 29 Oct 2003 15:00:18 +0000 Return-path: <[EMAIL PROTECTED]> Received: from mail.hcrest.net (mail.hcrest.com) [65.114.139.130] by master.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1AEro1-0004Eu-00; Wed, 29 Oct 2003 09:00:17 -0600 Received: from pobox.com ([10.1.3.25]) by mail.hcrest.com over TLS secured channel with Microsoft SMTPSVC(5.0.2195.5329); Wed, 29 Oct 2003 09:58:39 -0500 Message-ID: <[EMAIL PROTECTED]> Date: Wed, 29 Oct 2003 10:00:09 -0500 From: Bill Napier <[EMAIL PROTECTED]> User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5) Gecko/20031013 Thunderbird/0.3 X-Accept-Language: en-us, en MIME-Version: 1.0 To: [EMAIL PROTECTED] Subject: horde2 postinst error reporting Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 29 Oct 2003 14:58:39.0140 (UTC) FILETIME=[22D1D640:01C39E2D] Delivered-To: [EMAIL PROTECTED] X-Spam-Status: No, hits=-4.0 required=4.0 tests=BAYES_60,HAS_PACKAGE version=2.53-bugs.debian.org_2003_10_28 X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.53-bugs.debian.org_2003_10_28 (1.174.2.15-2003-03-30-exp) Package: horde2 Version: 2.2.3-1.1 It would be nice if the postinst script were to let the user know if there was a problem while configuring things (specifically database related things). The major thing that I noticed is that if postinst is unable to create the database (For whatever reason, ie: giving the wrong password...), it silently fails without any indication of a problem. I found this problem with the MySQL portion, but it seems to also be present at least with the Postgres part as well (at least from looking at the code). This was a problem because horde2 (and imp3) act kind of funny if they are configured to connect to a database but can't connect. After login, you get a message that you can't connect, but a refresh lets you keep going. Imp3 also puts out some other random error messages unrelated to database access. Once I put in the right information, all my problems cleared up.
--- End Message ---
--- Begin Message --->From [EMAIL PROTECTED] Sat Feb 04 07:37:12 2006 Received: (at 218183-done) by bugs.debian.org; 4 Feb 2006 15:37:12 +0000 Return-path: <[EMAIL PROTECTED]> Received: from c-adt-5.ataco.se ([213.115.168.248] helo=bixbite.opalsys.net) by spohr.debian.org with esmtp (Exim 4.50) id 1F5PTM-000184-27; Sat, 04 Feb 2006 07:37:12 -0800 Received: from ola by bixbite.opalsys.net with local (Exim 4.50) id 1F5PUf-0000aX-L0; Sat, 04 Feb 2006 16:38:33 +0100 Date: Sat, 4 Feb 2006 16:38:33 +0100 From: Ola Lundqvist <[EMAIL PROTECTED]> To: [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED] Subject: [EMAIL PROTECTED]: Bug#350630: fixed] Message-ID: <[EMAIL PROTECTED]> Reply-To: [EMAIL PROTECTED] Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.9i 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 Closing the bugs now as the packages have been removed from Debian. ----- Forwarded message from Debian Archive Maintenance <[EMAIL PROTECTED]> ----- Envelope-to: [EMAIL PROTECTED] Delivery-date: Thu, 02 Feb 2006 16:12:02 +0100 From: Debian Archive Maintenance <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] X-Katie: melanie $Revision: 1.44 $ Cc: [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED] Subject: Bug#350630: fixed X-Spam-Score: -2.5 (--) X-Spamcheck-provider: Checked for spam by opalsys.net, [EMAIL PROTECTED] We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: horde2 | 2.2.9-1 | source, all imp3 | 3.2.8-3 | source, all kronolith | 1.1.4-4 | source, all mnemo | 1.1.4-1 | source, all nag | 1.1.3-1 | source, all sork-accounts | 2.1.2-2 | source, all sork-forwards | 2.2.2-2 | source, all sork-passwd | 2.2.2-2 | source, all sork-vacation | 2.2.2-3 | source, all turba | 1.2.5-3 | source, all Note that the package(s) have simply been removed from the tag database and may (or may not) still be in the pool; this is not a bug. The package(s) will be physically removed automatically when no suite references them (and in the case of source, when no binary references it). Please also remember that the changes have been done on the master archive (ftp-master.debian.org) and will not propagate to any mirrors (ftp.debian.org included) until the next cron.daily run at the earliest. Packages are never removed from testing by hand. Testing tracks unstable and will automatically remove packages which were removed from unstable when removing them from testing causes no dependency problems. Bugs which have been reported against this package are not automatically removed from the Bug Tracking System. Please check all open bugs and close them or re-assign them to another package if the removed package was superseded by another one. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED] This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED] Debian distribution maintenance software pp. Joerg Jaspert (the ftpmaster behind the curtain) ----- End forwarded message ----- -- --------------------- Ola Lundqvist --------------------------- / [EMAIL PROTECTED] Annebergsslingan 37 \ | [EMAIL PROTECTED] 654 65 KARLSTAD | | +46 (0)54-10 14 30 +46 (0)70-332 1551 | | http://www.opal.dhs.org UIN/icq: 4912500 | \ gpg/f.p.: 7090 A92B 18FE 7994 0C36 4FE4 18A1 B1CF 0FE5 3DD9 / ---------------------------------------------------------------
--- End Message ---
