Your message dated Wed, 23 Feb 2005 12:53:10 +0100
with message-id <[EMAIL PROTECTED]>
and subject line O: distributed-net-pproxy -- Personal proxy for
distributed.net clients
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; 16 Dec 2004 21:43:11 +0000
>From [EMAIL PROTECTED] Thu Dec 16 13:43:11 2004
Return-path: <[EMAIL PROTECTED]>
Received: from merkel.debian.org [192.25.206.16] (mail)
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1Cf3Ox-0003YG-00; Thu, 16 Dec 2004 13:43:11 -0800
Received: from tbm by merkel.debian.org with local (Exim 3.35 1 (Debian))
id 1Cf3Ow-0005qN-00; Thu, 16 Dec 2004 14:43:10 -0700
Date: Thu, 16 Dec 2004 14:43:10 -0700
From: Martin Michlmayr <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: O: distributed-net-pproxy -- Personal proxy for distributed.net clients
Message-ID: <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.3.28i
X-Debbugs-CC: Stephen Stafford <[EMAIL PROTECTED]>
Sender: Martin Michlmayr <[EMAIL PROTECTED]>
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:
Package: wnpp
Severity: normal
distributed-net and distributed-net-pproxy were orphaned in #185016 but
only the former was adopted so the latter is still orphaned.
If you want to be the new maintainer, please take it -- see
http://www.debian.org/devel/wnpp/index.html#howto-o for
detailed instructions how to adopt a package properly.
Some information about this package:
Package: distributed-net-pproxy
Binary: distributed-net-pproxy
Version: 319c-7
Priority: optional
Section: non-free/misc
Maintainer: Debian QA Group <[EMAIL PROTECTED]>
Architecture: alpha i386 sparc
Standards-Version: 3.5.10
Format: 1.0
Directory: pool/non-free/d/distributed-net-pproxy
Files: 940f7c0a126aa5091311fc19116fa564 603 distributed-net-pproxy_319c-7.dsc
1d1331753418676e485b3b34d02540d3 722553 distributed-net-pproxy_319c.orig.tar.gz
81e113185325ecb1aed7bd827e5c6bcb 6122 distributed-net-pproxy_319c-7.diff.gz
Package: distributed-net-pproxy
Priority: optional
Section: non-free/misc
Installed-Size: 768
Maintainer: Debian QA Group <[EMAIL PROTECTED]>
Architecture: i386
Version: 319c-7
Suggests: distributed-net
Filename:
pool/non-free/d/distributed-net-pproxy/distributed-net-pproxy_319c-7_i386.deb
Size: 277932
MD5sum: 61d91f99188b6e578adce8f27791147d
Description: Personal proxy for distributed.net clients
With this proxy, you can serve v2 distributed.net RC5-64 & DES
clients. It allows you to establish one of your own machines as a
buffer between your clients and one of the keyservers that are
officially run by the distributed.net organizers. This will allow
your clients to waste less time trying to connect to one of the
main proxies, since the personal proxy will already have more key
blocks waiting for your clients when they're ready.
.
Running a personal proxy is definitely not needed by everyone, nor
is it recommended. You should only run a personal proxy if you are
very confident of your abilities, and you have a firewalled,
unreliable, or intermittent connection to the Internet to directly
contact one of the servers.
--
Martin Michlmayr
http://www.cyrius.com/
---------------------------------------
Received: (at 286010-done) by bugs.debian.org; 23 Feb 2005 11:53:11 +0000
>From [EMAIL PROTECTED] Wed Feb 23 03:53:11 2005
Return-path: <[EMAIL PROTECTED]>
Received: from 220pc220.sshunet.nl (mordor.wolffelaar.nl) [145.97.220.220]
(Debian-exim)
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1D3v4p-00082W-00; Wed, 23 Feb 2005 03:53:11 -0800
Received: from jeroen by mordor.wolffelaar.nl with local (Exim 4.34)
id 1D3v4o-0007qL-75
for [EMAIL PROTECTED]; Wed, 23 Feb 2005 12:53:10 +0100
Date: Wed, 23 Feb 2005 12:53:10 +0100
To: [EMAIL PROTECTED]
Subject: Re: O: distributed-net-pproxy -- Personal proxy for distributed.net
clients
Message-ID: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <[EMAIL PROTECTED]>
User-Agent: Mutt/1.5.6+20040907i
From: Jeroen van Wolffelaar <[EMAIL PROTECTED]>
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-Status: No, hits=-3.0 required=4.0 tests=BAYES_00 autolearn=no
version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level:
On Thu, Dec 16, 2004 at 02:43:10PM -0700, Martin Michlmayr wrote:
> distributed-net and distributed-net-pproxy were orphaned in #185016 but
> only the former was adopted so the latter is still orphaned.
In process of being removed (#290890), so not anymore up for adoption.
--Jeroen
--
Jeroen van Wolffelaar
[EMAIL PROTECTED]
http://jeroen.A-Eskwadraat.nl
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
