[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#156667: marked as done (ITA: fetchmail)



Your message dated Sun, 01 Sep 2002 02:52:06 -0400
with message-id <E17lOac-0006BQ-00@auric.debian.org>
and subject line Bug#156667: fixed in grisbi 0.3.2-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 2002 14:08:46 +0000
>From hmh@debian.org Wed Aug 14 09:08:46 2002
Return-path: <hmh@debian.org>
Received: from khazad-dum.debian.net [200.196.10.6] 
	by master.debian.org with esmtp (Exim 3.12 1 (Debian))
	id 17eypK-00009L-00; Wed, 14 Aug 2002 09:08:46 -0500
Received: by khazad-dum.debian.net (Postfix, from userid 1000)
	id 3A9D510406; Wed, 14 Aug 2002 11:08:45 -0300 (BRT)
Date: Wed, 14 Aug 2002 11:08:45 -0300
From: Henrique de Moraes Holschuh <hmh@debian.org>
To: Debian Bug Tracking System <submit@bugs.debian.org>
Subject: RFA: fetchmail
Message-ID: <20020814140845.GA22807@khazad-dum>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.4i
X-Reportbug-Version: 1.99.50
X-GPG-Fingerprint-1: 1024D/128D36EE 50AC 661A 7963 0BBA 8155  43D5 6EF7 F36B 128D 36EE
X-GPG-Fingerprint-2: 1024D/1CDB0FE3 5422 5C61 F6B7 06FB 7E04  3738 EE25 DE3F 1CDB 0FE3
Delivered-To: submit@bugs.debian.org

Package: wnpp
Version: N/A; reported 2002-08-14
Severity: normal

I am quite fed up of fetchmail, and thus not giving it the attention it
requires.  I am willing to orphan it, along with fetchmail-ssl... if someone
steps up to take care of it (after all, I do use it :P ).

Upstream is usually cooperative and easy to work with (Eric Raymond/ESR). He
does accept patches that break the hell out of fetchmail from time to time,
though.

The code is not too buggy, but it is nearly-unmaintaneable C (fetchmail) and
very maintaneable but quite large python (fetchmailconf).  IMHO (and in
upstream's) fetchmail actually needs to be rewritten from scratch in
something else than C.

Do not apply for adopting this package unless you have a lot of patience and
time to deal with the users and unexpected breakages. C knowledge is
required. You will have to deal with signal handling hell too, so be warned.

Whomever takes fetchmail, will also take fetchmail-ssl.  This is
non-negotiable: both packages come from the same source package (and should
probably be merged into a single one now that sarge is open, and
fetchmail-ssl is in main)...

-- System Information:
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux khazad-dum 2.4.18 #1 Sat May 11 19:16:08 BRT 2002 i686
Locale: LANG=pt_BR, LC_CTYPE=pt_BR

-- no debconf information


-- 
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh

---------------------------------------
Received: (at 156667-close) by bugs.debian.org; 1 Sep 2002 06:53:57 +0000
>From rdonald@auric.debian.org Sun Sep 01 01:53:57 2002
Return-path: <rdonald@auric.debian.org>
Received: from auric.debian.org [206.246.226.45] (mail)
	by master.debian.org with esmtp (Exim 3.12 1 (Debian))
	id 17lOcP-00088e-00; Sun, 01 Sep 2002 01:53:57 -0500
Received: from rdonald by auric.debian.org with local (Exim 3.35 1 (Debian))
	id 17lOac-0006BQ-00; Sun, 01 Sep 2002 02:52:06 -0400
From: Benjamin Drieu <benj@debian.org>
To: 156667-close@bugs.debian.org
X-Katie: $Revision: 1.17 $
Subject: Bug#156667: fixed in grisbi 0.3.2-1
Message-Id: <E17lOac-0006BQ-00@auric.debian.org>
Sender: Randall Donald <rdonald@auric.debian.org>
Date: Sun, 01 Sep 2002 02:52:06 -0400
Delivered-To: 156667-close@bugs.debian.org

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

grisbi_0.3.2-1.diff.gz
  to pool/main/g/grisbi/grisbi_0.3.2-1.diff.gz
grisbi_0.3.2-1.dsc
  to pool/main/g/grisbi/grisbi_0.3.2-1.dsc
grisbi_0.3.2-1_i386.deb
  to pool/main/g/grisbi/grisbi_0.3.2-1_i386.deb
grisbi_0.3.2.orig.tar.gz
  to pool/main/g/grisbi/grisbi_0.3.2.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 156667@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Benjamin Drieu <benj@debian.org> (supplier of updated grisbi 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, 20 Aug 2002 20:52:28 +0200
Source: grisbi
Binary: grisbi
Architecture: source i386
Version: 0.3.2-1
Distribution: unstable
Urgency: low
Maintainer: Benjamin Drieu <benj@debian.org>
Changed-By: Benjamin Drieu <benj@debian.org>
Description: 
 grisbi     - Personal finance tracking program based on GTK
Closes: 156667
Changes: 
 grisbi (0.3.2-1) unstable; urgency=low
 .
   * Initial Release.  (Closes: #156667)
Files: 
 342e00da15fd6aec52e3f189440f7b17 726 utils optional grisbi_0.3.2-1.dsc
 5c3eaa56f353e1506f6999d1de080af4 564890 utils optional grisbi_0.3.2.orig.tar.gz
 666eb507ede80e0b988b0aa435f155e2 3298 utils optional grisbi_0.3.2-1.diff.gz
 003c8d313c8ccfacc830c0889a882f2b 567454 utils optional grisbi_0.3.2-1_i386.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: Pour information voir http://www.gnupg.org

iD8DBQE9ZSNynDLqtZBL50ERApq8AJ9l58R0wb5X+6Lp/mR6XGie+eT21wCfcP//
ff+rSLzDj/KRSfSmuG7e44M=
=GCWD
-----END PGP SIGNATURE-----



Reply to: