Your message dated Mon, 3 Oct 2005 17:00:57 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Upload by maintainer
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; 11 Sep 2005 14:52:48 +0000
>From [EMAIL PROTECTED] Sun Sep 11 07:52:48 2005
Return-path: <[EMAIL PROTECTED]>
Received: from mail.lenk.info [217.160.183.176] 
        by spohr.debian.org with esmtp (Exim 3.36 1 (Debian))
        id 1EETCJ-0007Nr-00; Sun, 11 Sep 2005 07:52:48 -0700
Received: from smtp.lenk.info ([82.165.24.235] ident=Debian-exim)
        by mail.lenk.info with esmtpsa 
        (Cipher TLS-1.0:RSA_AES_256_CBC_SHA:32) (Exim 4.50 1)
        id 1EETGc-0002cD-Ix
        for <[EMAIL PROTECTED]>; Sun, 11 Sep 2005 16:57:14 +0200
Received: from vs5-deb.fnb.maschinenbau.tu-darmstadt.de ([130.83.174.41] 
helo=djpigpb.djpig.de)
        by smtp.lenk.info with esmtpsa 
        (Cipher TLS-1.0:RSA_AES_256_CBC_SHA:32) (Exim 4.50 1)
        id 1EETCJ-0007nv-Be
        for <[EMAIL PROTECTED]>; Sun, 11 Sep 2005 16:52:47 +0200
Received: from djpig by djpigpb.djpig.de with local (Exim 4.52)
        id 1EET63-0003zG-Mr
        for [EMAIL PROTECTED]; Sun, 11 Sep 2005 16:46:19 +0200
To: [EMAIL PROTECTED]
Subject: very old package with RC bugs, should this be orphaned?
Message-Id: <[EMAIL PROTECTED]>
From: Frank Lichtenheld <[EMAIL PROTECTED]>
Date: Sun, 11 Sep 2005 16:46:19 +0200
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-Level: 
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

Package: cookietool
Version: 2.5-1.1
Severity: serious

Hi.

During the Debian QA meeting hold during Sept. 09th till 11th, we
begun to go through the list of the oldest packages in Debian that are
not in testing (http://bjorn.haxx.se/debian/oldest.html) to
search for packages that should be either orphaned or removed
completly from Debian (unstable and testing) since they have been
obviously neglected by their maintainer.

Your package did show up on this list and we propose to orphan the package.

This usually means that your package matched some of the following criteria:

      [1] Your packages has not had an upload for more than two years

      [2] has one or more RC bugs with no answer from the maintainer (**)

      [3] the state of your packages in general seems to indicate that
      you might be MIA

      [4] (if we propose a removal) it shows in popcon as having less
          than 100 users with the package installed.

      [5] the package was not released with sarge

and at least ([1] and ( [2] or [3] or [4] or [5] )) was true.

(**) The maintainer not answering to RC bugs refers to bugs filed more
than one month before the time the check was performed.

In your case the package is older than 4 years and you didn't answer to
the gcc4 related bug (which is now RC) for over one year (I know it was
fixed yesterday evening by an NMU...).

After 7 days without answer from you (the maintainer) we will reassign
this bug to either WNPP (in case we propose to orphan it) or
ftp.debian.org (in case we propose to remove it).

The package will need an upload or an explanation for this action not
to proceed.

Please do *not* upload a package just to get off this list - it won't
help the package at all. Maintainers should be responsive and feel
responsible for their packages without needing other people to force
them to do work. Sometimes, finding a new maintainer or even removing
the package completly from the archive is better for Debian's users.

Thanks!
-- 
Frank Lichtenheld <[EMAIL PROTECTED]>

---------------------------------------
Received: (at 327661-done) by bugs.debian.org; 3 Oct 2005 15:03:08 +0000
>From [EMAIL PROTECTED] Mon Oct 03 08:03:08 2005
Return-path: <[EMAIL PROTECTED]>
Received: from mail.lenk.info [217.160.183.176] 
        by spohr.debian.org with esmtp (Exim 3.36 1 (Debian))
        id 1EMRqN-0001hV-00; Mon, 03 Oct 2005 08:03:08 -0700
Received: from smtp.lenk.info ([82.165.24.235] ident=Debian-exim)
        by mail.lenk.info with esmtpsa 
        (Cipher TLS-1.0:RSA_AES_256_CBC_SHA:32) (Exim 4.50 1)
        id 1EMRqp-000850-P1
        for <[EMAIL PROTECTED]>; Mon, 03 Oct 2005 17:03:35 +0200
Received: from p54a3cd0f.dip.t-dialin.net ([84.163.205.15] 
helo=djpigpb.djpig.de)
        by smtp.lenk.info with esmtpsa 
        (Cipher TLS-1.0:RSA_AES_256_CBC_SHA:32) (Exim 4.50 1)
        id 1EMRr1-0007fX-Dh
        for <[EMAIL PROTECTED]>; Mon, 03 Oct 2005 17:03:48 +0200
Received: from djpig by djpigpb.djpig.de with local (Exim 4.53)
        id 1EMRoH-0006cE-UF
        for [EMAIL PROTECTED]; Mon, 03 Oct 2005 17:00:57 +0200
Date: Mon, 3 Oct 2005 17:00:57 +0200
From: Frank Lichtenheld <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: Upload by maintainer
Message-ID: <[EMAIL PROTECTED]>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.11
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-Level: 
X-Spam-Status: No, hits=-3.0 required=4.0 tests=BAYES_00 autolearn=no 
        version=2.60-bugs.debian.org_2005_01_02

Maintainer has uploaded the package and acknowledged the NMU. Closing
this bug.

Gruesse,
-- 
Frank Lichtenheld <[EMAIL PROTECTED]>
www: http://www.djpig.de/


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

Reply via email to