[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#388252: marked as done (ITP: ffproxy -- A light and customizable http(s) proxy server with ipv6 support)



Your message dated Sun, 01 Oct 2006 05:15:17 -0700
with message-id <E1GU0E1-0005Qf-7A@spohr.debian.org>
and subject line Bug#388252: fixed in ffproxy 1.6-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: wnpp
Severity: wishlist
Owner: Emmanuel Bouthenot <kolter@openics.org>


* Package name    : ffproxy
  Version         : 1.6
  Upstream Author : Niklas Olmes <niklas@noxa.de>
* URL             : http://ffproxy.sf.net
* License         : GPL
  Programming Lang: C
  Description     : A light and customizable http(s) proxy server with ipv6 support

ffproxy is a filtering HTTP/HTTPS proxy server.
  - It is able to filter by host, URL, and header.
  - Custom header entries can be filtered and added.
  - It can even drop its privileges and be chrooted.
  - Logging to syslog() is supported.
  - It can use another auxiliary proxy server.
  - HTTP accelerator feature (acting as front-end to a HTTP server) is included.
  - It allows transparent IPv6 over IPv4 browsing (and vice versa).

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.17-2-k7
Locale: LANG=fr_FR@euro, LC_CTYPE=fr_FR@euro (charmap=ISO-8859-15)


--- End Message ---
--- Begin Message ---
Source: ffproxy
Source-Version: 1.6-1

We believe that the bug you reported is fixed in the latest version of
ffproxy, which is due to be installed in the Debian FTP archive:

ffproxy_1.6-1.diff.gz
  to pool/main/f/ffproxy/ffproxy_1.6-1.diff.gz
ffproxy_1.6-1.dsc
  to pool/main/f/ffproxy/ffproxy_1.6-1.dsc
ffproxy_1.6-1_amd64.deb
  to pool/main/f/ffproxy/ffproxy_1.6-1_amd64.deb
ffproxy_1.6.orig.tar.gz
  to pool/main/f/ffproxy/ffproxy_1.6.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 388252@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Emmanuel Bouthenot <kolter@openics.org> (supplier of updated ffproxy 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 ftpmaster@debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.7
Date: Mon, 11 Sep 2006 18:19:27 +0200
Source: ffproxy
Binary: ffproxy
Architecture: source amd64
Version: 1.6-1
Distribution: unstable
Urgency: low
Maintainer: Emmanuel Bouthenot <kolter@openics.org>
Changed-By: Emmanuel Bouthenot <kolter@openics.org>
Description: 
 ffproxy    - A light and customizable http(s) proxy server with ipv6 support
Closes: 388252
Changes: 
 ffproxy (1.6-1) unstable; urgency=low
 .
   * adding a patch which fix bug related to pid file creation
   * Initial release (Closes: #388252)
Files: 
 4e83dadcfbbeff6f4c87a4454058c51c 580 net optional ffproxy_1.6-1.dsc
 7fbb096671d859b9e2f069c8994f91c0 78222 net optional ffproxy_1.6.orig.tar.gz
 17c6bcb1dc8427f4db45b14b2d92e2ef 31042 net optional ffproxy_1.6-1.diff.gz
 2e410f5fc18ed23d8a766f6be52e87b4 39060 net optional ffproxy_1.6-1_amd64.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)

iD8DBQFFEUAEvGr7W6HudhwRAtTMAJ9hms3zZUnIH2iCXlXW8OvQcPusWQCgqZ9i
JR+jN86BCuyTw/yUArVGlTg=
=3M1k
-----END PGP SIGNATURE-----


--- End Message ---

Reply to: