Bug#165646: marked as done (RFP: libpam-securid -- standalone SecurID token server and PAM module)
Your message dated Wed, 14 Sep 2005 21:55:08 -0500 (CDT)
with message-id <20050915025508.5324A1079C9@cerdita.damog.net>
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; 20 Oct 2002 22:10:00 +0000
>From madduck@madduck.net Sun Oct 20 17:10:00 2002
Return-path: <madduck@madduck.net>
Received: from diamond.madduck.net [66.92.234.132]
by master.debian.org with esmtp (Exim 3.12 1 (Debian))
id 183OGl-0005jP-00; Sun, 20 Oct 2002 17:09:59 -0500
Received: from localhost (diamond.madduck.net [127.0.0.1])
by diamond.madduck.net (postfix) with ESMTP
id 2F59C1103A; Sun, 20 Oct 2002 18:09:25 -0400 (EDT)
Received: from fishbowl.madduck.net (dclient80-218-16-212.hispeed.ch [80.218.16.212])
(using TLSv1 with cipher EDH-RSA-DES-CBC3-SHA (168/168 bits))
(Client CN "fishbowl.madduck.net", Issuer "madduck.net CA" (verified OK))
by diamond.madduck.net (postfix) with ESMTP
id 0DAC211038; Sun, 20 Oct 2002 18:09:00 -0400 (EDT)
Received: by fishbowl.madduck.net (postfix, from userid 1000)
id 143C81AF17; Sun, 20 Oct 2002 21:22:51 +0200 (CEST)
Date: Sun, 20 Oct 2002 21:22:50 +0200
From: martin f krafft <madduck@debian.org>
To: Debian Bug Tracking System <submit@bugs.debian.org>
Cc: "E. Costin" <e_costin@users.sourceforge.net>
Subject: ITP: libpam-securid -- standalone SecurID token server and PAM module
Message-ID: <20021020192250.GA19338@fishbowl.madduck.net>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
protocol="application/pgp-signature"; boundary="fdj2RfSjLxBAspz7"
Content-Disposition: inline
User-Agent: Mutt/1.4i
X-Reportbug-Version: 1.50
X-Debbugs-CC: debian-devel@lists.debian.org
Organization: Debian GNU/Linux
X-OS: Debian GNU/Linux testing/unstable kernel 2.4.19-grsec-fishbowl i686
X-Motto: Keep the good times rollin'
X-Subliminal-Message: debian/rules!
X-Virus-Scanned: on diamond.madduck.net by AMaViS new-20020517
Delivered-To: submit@bugs.debian.org
X-Spam-Status: No, hits=-9.2 required=5.0
tests=NOSPAM_INC,PGP_SIGNATURE_2,SPAM_PHRASE_00_01,USER_AGENT,
USER_AGENT_MUTT
version=2.41
X-Spam-Level:
--fdj2RfSjLxBAspz7
Content-Type: text/plain; charset=iso-8859-15
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
Package: wnpp
Version: N/A; reported 2002-10-20
Severity: wishlist
* Package name : libpam-securid
Version : beta
Upstream Author : E. Costin <e_costin@users.sourceforge.net>
* URL : http://sourceforge.net/projects/securid-pam/
* License : GPL
Description : standalone SecurID token server and PAM module
I will monitor this module and upload it as soon as I managed to fit
it into my Debian's PAM.
-- System Information
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux fishbowl 2.4.19-grsec-fishbowl #1 Sat Sep 14 00:11:53 CEST 20=
02 i686
Locale: LANG=3Den_GB.ISO-8859-15, LC_CTYPE=3Dde_DE.ISO-8859-15
--=20
.''`. martin f. krafft <madduck@debian.org>
: :' : proud Debian developer, admin, and user
`. `'`
`- Debian - when you have better things to do than to fix a system
--fdj2RfSjLxBAspz7
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.0 (GNU/Linux)
iD8DBQE9swKKIgvIgzMMSnURAlOLAJ4gvpmMf+Oya11ktTbXHQvdpPWM8gCg3oz9
KyUnk44E8RtXSj6Bvx13apU=
=Xlrw
-----END PGP SIGNATURE-----
--fdj2RfSjLxBAspz7--
---------------------------------------
Received: (at 165646-done) by bugs.debian.org; 15 Sep 2005 02:55:28 +0000
>From damog@cerdita.damog.net Wed Sep 14 19:55:28 2005
Return-path: <damog@cerdita.damog.net>
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 1EFjuJ-0000P5-00; Wed, 14 Sep 2005 19:55:28 -0700
Received: by cerdita.damog.net (Postfix, from userid 1000)
id 5324A1079C9; Wed, 14 Sep 2005 21:55:08 -0500 (CDT)
To: 165646-done@bugs.debian.org
Subject: WNPP bug closed
Message-Id: <20050915025508.5324A1079C9@cerdita.damog.net>
Date: Wed, 14 Sep 2005 21:55:08 -0500 (CDT)
From: damog@cerdita.damog.net (David Moreno Garza)
Delivered-To: 165646-done@bugs.debian.org
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: 165
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 control@bugs.debian.org
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: <damog@debian.org>.
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 <damog@debian.org> Wed, 14 Sep 2005 21:54:42 -0500
Reply to: