Your message dated Mon, 08 Aug 2005 03:32:30 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#317801: fixed in proxychains 2.1-5
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 Jul 2005 15:58:15 +0000
>From [EMAIL PROTECTED] Mon Jul 11 08:58:15 2005
Return-path: <[EMAIL PROTECTED]>
Received: from postfix4-1.free.fr [213.228.0.62]
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1Ds0ff-0004TI-00; Mon, 11 Jul 2005 08:58:15 -0700
Received: from [127.0.0.1] (mut38-1-82-67-62-65.fbx.proxad.net [82.67.62.65])
by postfix4-1.free.fr (Postfix) with ESMTP id E23D83188C7;
Mon, 11 Jul 2005 17:58:13 +0200 (CEST)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: matthieu castet <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: proxychains: relocation error with libc from experimental
X-Mailer: reportbug 3.15
Date: Mon, 11 Jul 2005 17:58:13 +0200
Message-Id: <[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=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE
autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level:
Package: proxychains
Version: 2.1-4
Severity: normal
Tags: experimental
Hi,
with glibc from experiemental (2.3.5), proxuchain don't work anymore
and produce the error :
relocation error: /usr/lib/libproxychains.so: symbol __libc_connect, version
GLIBC_PRIVATE not defined in file libc.so.6 with link time reference
thanks
Matthieu
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/dash
Kernel: Linux 2.6.12
Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15)
Versions of packages proxychains depends on:
ii libc6 2.3.5-1 GNU C Library: Shared libraries an
proxychains recommends no packages.
-- no debconf information
---------------------------------------
Received: (at 317801-close) by bugs.debian.org; 8 Aug 2005 10:41:04 +0000
>From [EMAIL PROTECTED] Mon Aug 08 03:41:04 2005
Return-path: <[EMAIL PROTECTED]>
Received: from katie by spohr.debian.org with local (Exim 3.36 1 (Debian))
id 1E24vm-0006Hp-00; Mon, 08 Aug 2005 03:32:30 -0700
From: Rex Tsai <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
X-Katie: $Revision: 1.56 $
Subject: Bug#317801: fixed in proxychains 2.1-5
Message-Id: <[EMAIL PROTECTED]>
Sender: Archive Administrator <[EMAIL PROTECTED]>
Date: Mon, 08 Aug 2005 03:32:30 -0700
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=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER
autolearn=no version=2.60-bugs.debian.org_2005_01_02
Source: proxychains
Source-Version: 2.1-5
We believe that the bug you reported is fixed in the latest version of
proxychains, which is due to be installed in the Debian FTP archive:
proxychains_2.1-5.diff.gz
to pool/main/p/proxychains/proxychains_2.1-5.diff.gz
proxychains_2.1-5.dsc
to pool/main/p/proxychains/proxychains_2.1-5.dsc
proxychains_2.1-5_i386.deb
to pool/main/p/proxychains/proxychains_2.1-5_i386.deb
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Rex Tsai <[EMAIL PROTECTED]> (supplier of updated proxychains package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [EMAIL PROTECTED])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.7
Date: Sat, 6 Aug 2005 23:43:44 +0800
Source: proxychains
Binary: proxychains
Architecture: source i386
Version: 2.1-5
Distribution: unstable
Urgency: low
Maintainer: Rex Tsai <[EMAIL PROTECTED]>
Changed-By: Rex Tsai <[EMAIL PROTECTED]>
Description:
proxychains - proxy chains - redirect connections through proxy servers
Closes: 317801 321376
Changes:
proxychains (2.1-5) unstable; urgency=low
.
* applied patch from Klaus Ethgen <[EMAIL PROTECTED]>
* Fix a small error in which proxy forbite a connection.
* Removing white spaces from sources.
* Change the behavior on initial connection errors.
* Add "."'s to this changelog.
* Release proxys marked as down when list gets to small.
* Add handling of broken Proxies.
* Improve the random number generator.
* Improve the handling of down proxies.
* Fix problem in socks5 connection.
* Allow to save good proxies.
* Adding statistic capability replacing saving of good proxies.
* Halt process and reread config if too less proxies are available.
* Also allow the target to have a value.
* fixed undefined symbol: __libc_connect. (Closes: #317801)
* spelling corrected, thanks to Rakesh 'arky' Ambati <[EMAIL PROTECTED]>
(Closes: #321376)
Files:
61e928ec61bd231fd527116cd309fdc2 637 net optional proxychains_2.1-5.dsc
209a0d2ab12b0f4449c1536b9af321b7 388543 net optional proxychains_2.1-5.diff.gz
1d271df25b5f79f71a6fbab883330709 17136 net optional proxychains_2.1-5_i386.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
iEYEARECAAYFAkL3JzoACgkQIgvIgzMMSnWuMgCgwiKF67DstRWdSqYRJR+pEOKh
iJsAoNXEokPX06TNLZXHBVTTgQTKi9r6
=nT7L
-----END PGP SIGNATURE-----
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
