Your message dated Wed, 14 Sep 2005 21:55:03 -0500 (CDT)
with message-id <[EMAIL PROTECTED]>
and subject line WNPP bug closed
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; 4 Nov 2001 04:10:51 +0000
>From [EMAIL PROTECTED] Sat Nov 03 22:10:51 2001
Return-path: <[EMAIL PROTECTED]>
Received: from mlf.linux.rulez.org [192.188.244.13] 
        by master.debian.org with esmtp (Exim 3.12 1 (Debian))
        id 160EcU-0001vD-00; Sat, 03 Nov 2001 22:10:50 -0600
Received: from mlf.linux.rulez.org (mlf.linux.rulez.org [192.188.244.13])
        by mlf.linux.rulez.org (Postfix) with ESMTP
        id 6D1D28B972; Sun,  4 Nov 2001 05:10:34 +0100 (CET)
Date: Sun, 4 Nov 2001 05:10:32 +0100 (CET)
From: Tamas SZERB <[EMAIL PROTECTED]>
X-Sender: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Cc: debian-devel@lists.debian.org
Subject: ITP: silc -- Secure Internet Live Conferencing
Message-ID: <[EMAIL PROTECTED]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Delivered-To: [EMAIL PROTECTED]

Package: wnpp
Severity: wishlist

I intend to package called silc, that means 4 sparated packages currently.
They are silc-client, silc-server, libsilc, and libsilc-dev.
NB. these packages contain strong encryptions, thus they will go into the
non-US distrib.

Package: silc
License: GPL
URL: http://www.silcnet.org/

Description:
-----------------
Description: SILC - Secure Internet Live Conferencing
 SILC (Secure Internet Live Conferencing) is a protocol which provides
 secure conferencing services in the Internet over insecure channel.
 SILC is IRC like softwarre although internally they are very different.
 Biggest similarity between SILC and IRC is that they both provide
 conferencing services and that SILC has almost same commands as IRC.  Other
 than that they are nothing alike.  Biggest differences are that SILC is
 secure what IRC is not in any way.  The network model is also entirely
 different compared to IRC.

--
VWOL
Tamas SZERB <[EMAIL PROTECTED]>
GPG public key: http://alabama.inf.elte.hu/~toma/gpgkey.asc
PGP public key: http://alabama.inf.elte.hu/~toma/pgpkey.asc





---------------------------------------
Received: (at 118202-done) by bugs.debian.org; 15 Sep 2005 02:55:15 +0000
>From [EMAIL PROTECTED] Wed Sep 14 19:55:15 2005
Return-path: <[EMAIL PROTECTED]>
Received: from dsl-201-129-37-187.prod-infinitum.com.mx (cerdita.damog.net) 
[201.129.37.187] 
        by spohr.debian.org with esmtp (Exim 3.36 1 (Debian))
        id 1EFju5-0000NS-00; Wed, 14 Sep 2005 19:55:14 -0700
Received: by cerdita.damog.net (Postfix, from userid 1000)
        id E250C1078AB; Wed, 14 Sep 2005 21:55:03 -0500 (CDT)
To: [EMAIL PROTECTED]
Subject: WNPP bug closed
Message-Id: <[EMAIL PROTECTED]>
Date: Wed, 14 Sep 2005 21:55:03 -0500 (CDT)
From: [EMAIL PROTECTED] (David Moreno Garza)
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=-5.0 required=4.0 tests=BAYES_00,VALID_BTS_CONTROL 
        autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-CrossAssassin-Score: 46

Hello,

This is an automatic mail sent to close the RFP you have reported or 
are involved with.

Your RFP wnpp bug is being closed because of the following reasons:
- It is, as of today, older than 600 days.
- It haven't had any activity recently.
- The amount of ITPs on the Debian BTS is huge and we need to
  clean up a bit the place.

As this an automatic procedure, it could of course have something
wrong and probably it would be closing some bugs that are not 
intended by owners and submitters (like you) to be closed, for
example if the RFP is still of your interest, or there has been 
some kind of activity around it. In that case, please reopen the
bug, do it, DO IT NOW! (I don't want to be blamed because of
mass closing and not let people know that they can easily reopen
their bugs ;-).

To re-open it, you simply have to mail [EMAIL PROTECTED]
with a body text like this:

reopen 123456
thanks bts

Replacing '123456' for the number of your RFP bug. The subject of the
mail is ignored. Or if you have any kind of problems when dealing with
the BTS, feel free to contact me and I'd be more than happy to help
you on this: <[EMAIL PROTECTED]>.

This is the first mass wnpp closing that will be done. The next close
will be done on inactive RFPs older than 450 days and finally, the
ones older than 365 days (an automatic script will close *inactive*
RFPs when they reach one year old).

A similar process is being applied to the ITP wnpp bugs in these
days.

Thanks for your cooperation,

 -- David Moreno Garza <[EMAIL PROTECTED]>  Wed, 14 Sep 2005 21:54:42 -0500


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

Reply via email to