Your message dated Tue, 06 Mar 2007 21:32:02 +0000
with message-id <[EMAIL PROTECTED]>
and subject line Bug#396729: fixed in scavr 1.8.2-1
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)
--- Begin Message ---
Package: scavr
Version: 1.7.0-2
Severity: important
Hi,
You see my software versions below.
In fact, I just add
url_rewrite_program /usr/lib/squid/scavr -c /etc/squid/scavr.conf
url_rewrite_children 1
url_rewrite_access deny localhost
into my squid.conf, then restart squid, then run strace on
'python scavr' process. I see that on first squid request, python
reads characters from stdin, byte by byte, but it does not return
on reading newline:
read(0, "h", 1) = 1
read(0, "t", 1) = 1
read(0, "t", 1) = 1
read(0, "p", 1) = 1
read(0, ":", 1) = 1
read(0, "/", 1) = 1
read(0, "/", 1) = 1
read(0, "s", 1) = 1
...
read(0, "G", 1) = 1
read(0, "E", 1) = 1
read(0, "T", 1) = 1
read(0, " ", 1) = 1
read(0, "-", 1) = 1
read(0, "\n", 1) = 1
read(0, <unfinished ...>
(I had broken the last read)
Looking into lsof, I can see that squid spawns python-scavr with
unix domain sockets as its stdin and stdout. May be python works
with sockets in some special way, but so far I could not find
this out of python sources. Hope you would.
Thank you in advance for your attention to this.
-- System Information:
Debian Release: 4.0
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'stable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-1-686
Locale: LANG=uk_UA.UTF-8, LC_CTYPE=uk_UA.UTF-8 (charmap=UTF-8)
Versions of packages scavr depends on:
ii python 2.4.4-1 An interactive high-level object-o
ii python-clamav 0.3.3-2 Python bindings to ClamAV
Versions of packages scavr recommends:
ii squid 2.6.4-2 Internet Object Cache (WWW proxy c
-- no debconf information
--- End Message ---
--- Begin Message ---
Source: scavr
Source-Version: 1.8.2-1
We believe that the bug you reported is fixed in the latest version of
scavr, which is due to be installed in the Debian FTP archive:
scavr_1.8.2-1.diff.gz
to pool/main/s/scavr/scavr_1.8.2-1.diff.gz
scavr_1.8.2-1.dsc
to pool/main/s/scavr/scavr_1.8.2-1.dsc
scavr_1.8.2-1_all.deb
to pool/main/s/scavr/scavr_1.8.2-1_all.deb
scavr_1.8.2.orig.tar.gz
to pool/main/s/scavr/scavr_1.8.2.orig.tar.gz
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.
Cédric Delfosse <[EMAIL PROTECTED]> (supplier of updated scavr 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: Sun, 25 Feb 2007 15:56:40 +0100
Source: scavr
Binary: scavr
Architecture: source all
Version: 1.8.2-1
Distribution: experimental
Urgency: low
Maintainer: Cédric Delfosse <[EMAIL PROTECTED]>
Changed-By: Cédric Delfosse <[EMAIL PROTECTED]>
Description:
scavr - Squid ClamAV Redirector
Closes: 396729
Changes:
scavr (1.8.2-1) experimental; urgency=low
.
* New upstream release
* Apply patch to make it works with squid 2.6 (Closes: Bug#396729)
Files:
83e33aaa2c543dd3e627e2793e1efa39 575 web optional scavr_1.8.2-1.dsc
777c761b59348a22596054e59dc8f6d4 6888 web optional scavr_1.8.2.orig.tar.gz
8cf71372230107bab91e80b5c4ff8372 3132 web optional scavr_1.8.2-1.diff.gz
73853a855576b6c08230ad9cf66453dd 9664 web optional scavr_1.8.2-1_all.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFF7dr3bmmXPPfovGMRAro5AKDRqJXVI8WirUqLl6xMoMrE0LDN4QCePsVQ
vTYskO6hceYni3T1O5Lavmo=
=bfGB
-----END PGP SIGNATURE-----
--- End Message ---
