Your message dated Thu, 11 Aug 2005 13:17:26 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#322229: fixed in spkproxy 1.4.8-2
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; 9 Aug 2005 21:06:03 +0000
>From [EMAIL PROTECTED] Tue Aug 09 14:06:03 2005
Return-path: <[EMAIL PROTECTED]>
Received: from smtp3.wanadoo.fr [193.252.22.28]
by spohr.debian.org with esmtp (Exim 3.36 1 (Debian))
id 1E2bIR-0001q2-00; Tue, 09 Aug 2005 14:06:03 -0700
Received: from me-wanadoo.net (localhost [127.0.0.1])
by mwinf0308.wanadoo.fr (SMTP Server) with ESMTP id 485E5200008B
for <[EMAIL PROTECTED]>; Tue, 9 Aug 2005 23:05:32 +0200 (CEST)
Received: from localhost.localdomain (ARennes-351-1-2-59.w82-126.abo.wanadoo.fr
[82.126.32.59])
by mwinf0308.wanadoo.fr (SMTP Server) with ESMTP id 06010200008A;
Tue, 9 Aug 2005 23:05:31 +0200 (CEST)
X-ME-UUID: [EMAIL PROTECTED]
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-15"
From: Sylvain <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: ImportError: No module named timeoutsocke
X-Mailer: reportbug 3.15
Date: Tue, 09 Aug 2005 23:05:30 +0200
Message-Id: <[EMAIL PROTECTED]>
Content-Transfer-Encoding: quoted-printable
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=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE
autolearn=no version=2.60-bugs.debian.org_2005_01_02
Package: spikeproxy
Version: 1.4.8-1
Severity: grave
Justification: renders package unusable
Hi,
When I launch spikeproxy, I have this error:
n# spikeproxy=20
Traceback (most recent call last):
File "spkproxy.py", line 49, in ?
import spikeProxyUI=20
File "/usr/share/spikeproxy/spikeProxyUI.py", line 39, in ?
from requestandresponse import RequestAndResponse
File "/usr/share/spikeproxy/requestandresponse.py", line 4, in ?
import daveutil
File "/usr/share/spikeproxy/daveutil.py", line 12, in ?
import spkproxy=B2
File "/usr/share/spikeproxy/spkproxy.py", line 54, in ?
import timeoutsocket
ImportError: No module named timeoutsocket
So spikeproxy can't run.
Rgds
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.12
Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=3DISO-8859-15)
Versions of packages spikeproxy depends on:
ii python 2.3.5-3 An interactive high-level ob=
ject-o
ii python-pyopenssl 0.6-2 Python wrapper around the Op=
enSSL=20
spikeproxy recommends no packages.
-- no debconf information
---------------------------------------
Received: (at 322229-close) by bugs.debian.org; 11 Aug 2005 20:22:03 +0000
>From [EMAIL PROTECTED] Thu Aug 11 13:22:03 2005
Return-path: <[EMAIL PROTECTED]>
Received: from katie by spohr.debian.org with local (Exim 3.36 1 (Debian))
id 1E3JUU-0005Q5-00; Thu, 11 Aug 2005 13:17:26 -0700
From: Javier Fernandez-Sanguino Pen~a <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
X-Katie: $Revision: 1.56 $
Subject: Bug#322229: fixed in spkproxy 1.4.8-2
Message-Id: <[EMAIL PROTECTED]>
Sender: Archive Administrator <[EMAIL PROTECTED]>
Date: Thu, 11 Aug 2005 13:17:26 -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: spkproxy
Source-Version: 1.4.8-2
We believe that the bug you reported is fixed in the latest version of
spkproxy, which is due to be installed in the Debian FTP archive:
spikeproxy_1.4.8-2_all.deb
to pool/main/s/spkproxy/spikeproxy_1.4.8-2_all.deb
spkproxy_1.4.8-2.diff.gz
to pool/main/s/spkproxy/spkproxy_1.4.8-2.diff.gz
spkproxy_1.4.8-2.dsc
to pool/main/s/spkproxy/spkproxy_1.4.8-2.dsc
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.
Javier Fernandez-Sanguino Pen~a <[EMAIL PROTECTED]> (supplier of updated
spkproxy 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: Thu, 11 Aug 2005 20:48:04 +0200
Source: spkproxy
Binary: spikeproxy
Architecture: source all
Version: 1.4.8-2
Distribution: unstable
Urgency: low
Maintainer: Javier Fernandez-Sanguino Pen~a <[EMAIL PROTECTED]>
Changed-By: Javier Fernandez-Sanguino Pen~a <[EMAIL PROTECTED]>
Description:
spikeproxy - Web application security testing proxy
Closes: 322229
Changes:
spkproxy (1.4.8-2) unstable; urgency=low
.
* Add timeoutsocked and read_query to the Makefile's python files
to install (Closes: #322229
Files:
be8ad18ae654fb5be3d36e50aa58a4c6 710 net optional spkproxy_1.4.8-2.dsc
c4a90620a12b6c3d1c4506864e9d1d7b 7790 net optional spkproxy_1.4.8-2.diff.gz
4b14052ac552ae51ebcc9e02a878d417 599144 net optional spikeproxy_1.4.8-2_all.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
iQCVAwUBQvueGvtEPvakNq0lAQLn/wQAqJZe4HMePst+T1ByONNyYXiJ3wk2ki+U
KuG7ViI+59ldlOgAnfj1BHDfYh1dLmgeJvgAaamigfeGs8KHxUvmFWDb9vhDsc+d
sD3v+IEeEB2QyQ08qa8JcJ4z45FuIUtuYZMEuitmnk3UUUfu2HmNfjYhY20SE0KT
vxynyaFQ9Us=
=bU7z
-----END PGP SIGNATURE-----
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
