Your message dated Wed, 16 Mar 2005 13:35:57 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#265622: fixed in up-imapproxy 1.2.3-1
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; 14 Aug 2004 01:35:20 +0000
>From [EMAIL PROTECTED] Fri Aug 13 18:35:20 2004
Return-path: <[EMAIL PROTECTED]>
Received: from mail.irb.hr [161.53.22.8] (UNKNOWN)
        by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
        id 1BvnS3-00009c-00; Fri, 13 Aug 2004 18:35:19 -0700
Received: from localhost (localhost [127.0.0.1])
        by mail.irb.hr (8.12.9/8.12.9/Debian-5) with ESMTP id i7E1ZEud017458;
        Sat, 14 Aug 2004 03:35:14 +0200
Received: from rctest.irb.hr (rctest.irb.hr [161.53.128.35])
        by mail.irb.hr (8.12.9/8.12.9/Debian-5) with ESMTP id i7E1Z9NJ017452;
        Sat, 14 Aug 2004 03:35:09 +0200
Received: from rctest.irb.hr (localhost [127.0.0.1])
        by rctest.irb.hr (8.12.11/8.12.11/Debian-5) with ESMTP id 
i7E1ZAXU011049;
        Sat, 14 Aug 2004 03:35:10 +0200
Received: (from [EMAIL PROTECTED])
        by rctest.irb.hr (8.12.11/8.12.11/Debian-5) id i7E1ZAcA011047;
        Sat, 14 Aug 2004 03:35:10 +0200
Date: Sat, 14 Aug 2004 03:35:10 +0200
From: Andelko Horvat <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: imapproxy: bad init script
Message-ID: <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="k1lZvvs/B4yU6o8G"
Content-Disposition: inline
User-Agent: Mutt/1.3.28i
X-Reportbug-Version: 2.63
X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at irb.hr
Delivered-To: [EMAIL PROTECTED]
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=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE 
        autolearn=no version=2.60-bugs.debian.org_2004_03_25
X-Spam-Level: 


--k1lZvvs/B4yU6o8G
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

Package: imapproxy
Version: 1.2.1-2
Severity: normal


You can't use start-stop-daemon with option --pidfile, because imapproxy
doesn't create pidfile. I recommend the attached init script.


-- System Information:
Debian Release: 3.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.4.24-1-686
Locale: LANG=C, LC_CTYPE=C

Versions of packages imapproxy depends on:
ii  debconf                     1.4.30       Debian configuration management sy
ii  libc6                       2.3.2.ds1-13 GNU C Library: Shared libraries an
ii  libncurses5                 5.4-4        Shared libraries for terminal hand
ii  libssl0.9.7                 0.9.7d-4     SSL shared libraries
ii  libwrap0                    7.6.dbs-4    Wietse Venema's TCP wrappers libra

-- debconf information:
* imapproxy/imap-server: localhost

--k1lZvvs/B4yU6o8G
Content-Type: text/plain; charset=us-ascii
Content-Disposition: attachment; filename=imapproxy

#! /bin/sh
# Initfile for imapproxy
#
# skeleton      example file to build /etc/init.d/ scripts.
#               This file should be used to construct scripts for /etc/init.d.
#
#               Written by Miquel van Smoorenburg <[EMAIL PROTECTED]>.
#               Modified for Debian GNU/Linux
#               by Ian Murdock <[EMAIL PROTECTED]>.
#
# Version:      @(#)skeleton  1.8  03-Mar-1998  [EMAIL PROTECTED]
# Customized for UP-ImapProxy by Jose Luis Tallon <[EMAIL PROTECTED]>

PATH=/sbin:/bin:/usr/sbin:/usr/bin

DAEMON=/usr/sbin/imapproxyd
ARGS="-f /etc/imapproxy.conf"
NAME="imapproxy"
DESC="IMAP proxy"

test -f $DAEMON || exit 0

set -e

case "$1" in
  start)
        echo -n "Starting $DESC: $NAME"
        start-stop-daemon --start --oknodo --quiet --exec $DAEMON -- $ARGS
        echo .
        ;;
  stop)
        echo -n "Stopping $DESC: $NAME"
        start-stop-daemon --stop --oknodo --quiet --exec $DAEMON >/dev/null
        echo .
        ;;
  restart|force-reload)
        echo -n "Restarting $DESC: $NAME"
        start-stop-daemon --stop --oknodo --quiet --exec $DAEMON >/dev/null
        sleep 1
        start-stop-daemon --start --oknodo --quiet --exec $DAEMON -- $ARGS
        echo .
        ;;
  *)
        echo "Usage: $0 {start|stop|restart|force-reload}" >&2
        exit 1
        ;;
esac

--k1lZvvs/B4yU6o8G--

---------------------------------------
Received: (at 265622-close) by bugs.debian.org; 16 Mar 2005 18:53:17 +0000
>From [EMAIL PROTECTED] Wed Mar 16 10:53:17 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 1DBdds-0005lI-00; Wed, 16 Mar 2005 10:53:17 -0800
Received: from katie by newraff.debian.org with local (Exim 3.35 1 (Debian))
        id 1DBdN7-0004nN-00; Wed, 16 Mar 2005 13:35:57 -0500
From: Jose Luis Tallon <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
X-Katie: $Revision: 1.55 $
Subject: Bug#265622: fixed in up-imapproxy 1.2.3-1
Message-Id: <[EMAIL PROTECTED]>
Sender: Archive Administrator <[EMAIL PROTECTED]>
Date: Wed, 16 Mar 2005 13:35:57 -0500
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: up-imapproxy
Source-Version: 1.2.3-1

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

imapproxy_1.2.3-1_i386.deb
  to pool/main/u/up-imapproxy/imapproxy_1.2.3-1_i386.deb
up-imapproxy_1.2.3-1.diff.gz
  to pool/main/u/up-imapproxy/up-imapproxy_1.2.3-1.diff.gz
up-imapproxy_1.2.3-1.dsc
  to pool/main/u/up-imapproxy/up-imapproxy_1.2.3-1.dsc
up-imapproxy_1.2.3.orig.tar.gz
  to pool/main/u/up-imapproxy/up-imapproxy_1.2.3.orig.tar.gz



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.
Jose Luis Tallon <[EMAIL PROTECTED]> (supplier of updated up-imapproxy 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: Sun, 13 Mar 2005 01:43:16 +0100
Source: up-imapproxy
Binary: imapproxy
Architecture: source i386
Version: 1.2.3-1
Distribution: unstable
Urgency: low
Maintainer: Jose Luis Tallon <[EMAIL PROTECTED]>
Changed-By: Jose Luis Tallon <[EMAIL PROTECTED]>
Description: 
 imapproxy  - IMAP protocol proxy
Closes: 265622 287542
Changes: 
 up-imapproxy (1.2.3-1) unstable; urgency=low
 .
   * New upstream version
 .
   * Corrected init script (Closes: #265622)
 .
   * Added Czech translation (Closes: #287542)
 .
   * Package sponsored by Roberto Lumbreras <[EMAIL PROTECTED]>
Files: 
 41272ab28a755809bade51420d8b8cdd 670 mail extra up-imapproxy_1.2.3-1.dsc
 ad4dafd1417903feb1e09ec569ff1ad5 122991 mail extra 
up-imapproxy_1.2.3.orig.tar.gz
 8feff6cd6bd3a2b12d402c74a039939f 7669 mail extra up-imapproxy_1.2.3-1.diff.gz
 597a8221ade6ec09cdaab26aeaa22a1a 49092 mail extra imapproxy_1.2.3-1_i386.deb

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

iD8DBQFCOHbSfIEQE/XJcI0RAmGDAKDZlYcZXSI2pCE4nbPaI98UzsTs/wCg9pCZ
710A1oiOmLDcVMZ1iJdzGOc=
=gpeQ
-----END PGP SIGNATURE-----


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

Reply via email to