Your message dated Thu, 22 Sep 2005 17:17:45 -0600
with message-id <[EMAIL PROTECTED]>
and subject line WNPP bug closing
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; 6 Jul 2004 16:37:49 +0000
>From [EMAIL PROTECTED] Tue Jul 06 09:37:49 2004
Return-path: <[EMAIL PROTECTED]>
Received: from rwcrmhc11.comcast.net [204.127.198.35]
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1Bhsx3-0008UW-00; Tue, 06 Jul 2004 09:37:49 -0700
Received: from mirrorlynx.com ([68.82.164.103])
by comcast.net (rwcrmhc11) with ESMTP
id <2004070616371901300jjf2se>
(Authid: cwizard13);
Tue, 6 Jul 2004 16:37:19 +0000
Received: from dan by mirrorlynx.com with local (Exim 4.34)
id 1Bhswt-0008Cb-1c; Tue, 06 Jul 2004 12:37:41 -0400
Date: Tue, 6 Jul 2004 12:37:39 -0400
From: Dan Weber <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Message-ID: <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Disposition: inline
X-Reportbug-Version: 2.58
X-Debbugs-Cc: debian-devel@lists.debian.org
X-Operating-System: Debian GNU/Linux testing/unstable 2.6.7-1-k7
X-Editor: GNU Emacs 21.3.1
X-MailServer: Exim 4.34-1
User-Agent: Mutt/1.5.5.1+cvs20040105i
X-SA-Exim-Connect-IP: <locally generated>
X-SA-Exim-Rcpt-To: [EMAIL PROTECTED], [EMAIL PROTECTED]
X-SA-Exim-Mail-From: [EMAIL PROTECTED]
Subject: ITP: libodbcxx -- C++ class library for accessing SQL databases via
ODBC
Content-Type: multipart/signed; micalg=pgp-sha1;
protocol="application/pgp-signature"; boundary="fUYQa+Pmc3FrFX/N"
X-Spam-DCC: mirrorlynx1: mirrorlynx.com 1000; Body=1 Fuz1=1 Fuz2=1
X-Spam-Pyzor: Reported 0 times.
X-SA-Exim-Version: 4.0 (built Sat, 24 Apr 2004 12:31:30 +0200)
X-SA-Exim-Scanned: Yes (on mirrorlynx.com)
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=-11.0 required=4.0 tests=BAYES_00,HAS_PACKAGE,
X_DEBBUGS_CC autolearn=ham version=2.60-bugs.debian.org_2004_03_25
X-Spam-Level:
--fUYQa+Pmc3FrFX/N
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Package: wnpp
Severity: wishlist
* Package name : libodbcxx
Version : 0.2.3
Upstream Author : Manush Dodunekov <[EMAIL PROTECTED]>
* URL : http://libodbcxx.sourceforge.net/
* License : LGPL
Description : C++ class library for accessing SQL databases via ODBC
Libodbc++ is a c++ class library for accessing SQL databases. It is
designed with standards in mind, so it provides a subset of the
well-known JDBC 2.0(tm) and runs on top of ODBC. It integrates well
with STL, which it is also based after.
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable'), (499, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.7-1-k7
Locale: LANG=en_US, LC_CTYPE=en_US
--fUYQa+Pmc3FrFX/N
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
iD8DBQFA6tVQF6i3K/AxoQERAlK6AKCzjxHQrpxX24HPnxS2RM5rishHDACfeZOi
q9NcSPDUBK/UCCqcSDL7QGs=
=XkyZ
-----END PGP SIGNATURE-----
--fUYQa+Pmc3FrFX/N--
---------------------------------------
Received: (at 257914-done) by bugs.debian.org; 22 Sep 2005 23:17:45 +0000
>From [EMAIL PROTECTED] Thu Sep 22 16:17:45 2005
Return-path: <[EMAIL PROTECTED]>
Received: from merkel.debian.org [192.25.206.16] (mail)
by spohr.debian.org with esmtp (Exim 3.36 1 (Debian))
id 1EIaK1-0000wb-00; Thu, 22 Sep 2005 16:17:45 -0700
Received: from damog by merkel.debian.org with local (Exim 3.36 1 (Debian))
id 1EIaK1-0006jr-00; Thu, 22 Sep 2005 17:17:45 -0600
To: [EMAIL PROTECTED]
Subject: WNPP bug closing
Message-Id: <[EMAIL PROTECTED]>
From: David Moreno Garza <[EMAIL PROTECTED]>
Date: Thu, 22 Sep 2005 17:17:45 -0600
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
Hello,
This is an automatic mail sent to close the ITP you have reported or
are involved with.
Your ITP wnpp bug is being closed because of the following reasons:
- It is, as of today, older than 365 days.
- It hasn't had any activity recently.
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 ITP 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 257914
thanks bts
Further comments on the work done in the bug sent to
[EMAIL PROTECTED] would be truly welcomed.
Anyway, 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 second massive wnpp closing that is being done. The next close
will be done on inactive ITPs older than 365 days and finally, an automatic
script will close, by default, *inactive* ITPs when they reach one year of
inactivity.
A similar process is being applied to other kind of wnpp bugs.
Thanks for your cooperation,
-- David Moreno Garza <[EMAIL PROTECTED]> Thu, 22 Sep 2005 17:06:42 -0500
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
