Your message dated Tue, 15 Dec 2009 03:28:13 +0100
with message-id <[email protected]>
and subject line Re: Bug#560829: privoxy: lenny/amd64 package is missing IPv6 
support
has caused the Debian Bug report #560829,
regarding privoxy: lenny/amd64 package is missing IPv6 support
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
560829: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=560829
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: privoxy
Version: 3.0.15-1
Severity: normal
Tags: ipv6

hi,

the lenny/amd64 version of privoxy is missing IPv6 support,
but on lenny/i386 it works just fine. Rebuilding the package
on lenny/amd64 fixes the problem. The amd64 version is a
maintainer-build while i386 got autobuild
http://packages.qa.debian.org/p/privoxy/news/20080707T211718Z.html
Probably unclean build-environment?

cu
Maurice Massar

-- System Information:
Debian Release: 5.0.3
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.28-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=ja_JP.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages privoxy depends on:
ii  adduser                3.110             add and remove users and groups
ii  libc6                  2.7-18            GNU C Library: Shared libraries
ii  libpcre3               7.6-2.1           Perl 5 Compatible Regular Expressi
ii  logrotate              3.7.1-5           Log rotation utility
ii  lsb-base               3.2-20            Linux Standard Base 3.2 init scrip
ii  perl                   5.10.0-19lenny2   Larry Wall's Practical Extraction 
ii  zlib1g                 1:1.2.3.3.dfsg-12 compression library - runtime

Versions of packages privoxy recommends:
pn  doc-base                      <none>     (no description available)

privoxy suggests no packages.

-- no debconf information



--- End Message ---
--- Begin Message ---
hi,

On Sat, Dec 12, 2009 at 06:54:46PM +0100, Roland Rosenfeld wrote:
> Maurice Massar schrieb am Samstag, den 12. Dezember 2009:
> > Package: privoxy
> > Version: 3.0.15-1
> > Severity: normal
> > Tags: ipv6
> 
> > the lenny/amd64 version of privoxy is missing IPv6 support,
> > but on lenny/i386 it works just fine. Rebuilding the package
> > on lenny/amd64 fixes the problem. The amd64 version is a
> > maintainer-build while i386 got autobuild
> > http://packages.qa.debian.org/p/privoxy/news/20080707T211718Z.html
> > Probably unclean build-environment?
> 
> Very strange.  I use exactly this amd64 build version on my own
> workstation and IPv6 is supported and works correct.
> http://p.p/show-status shows, that FEATURE_IPV6_SUPPORT is enabled.
> 
> Could you please tell me how you detected that IPv6 is missing?
> 
> BTW: What version are you talking about exactly? 3.0.15-1 (sid) as
> mentioned above or 3.0.9-1 as mentioned in the above link?
> 
> As you can see in changelog.Debian 3.0.10-2 was the first version with
> IPv6 support (except an intermezzo with 3.0.5-beta-1 and -2, that was
> some kind of disaster, so I removed it in 3.0.5-beta-3).  So 3.0.9-1
> should never support IPv6...

sorry, I was wrong right from start. I've just test .6-2/.9-1/.12-2/.15-1/.15-2
(ie. all versions in the regular archive) on i386 & amd64, and it is as
you say, v6 support starts with .12, no mismatch between archs.

To verify, I did apt-get source, debuild ... but I've got a deb-src line
for unstable on my lenny box, which explains both why I was talking
about 3.0.9-1 while I actually had 3.0.15-1 on an otherwise lenny
machine...

anyway, thanks for maintaining the privoxy package
.. and bearing with me (-;
cu
Maurice Massar


--- End Message ---

Reply via email to