Hi Carl!
On Sat, 29 Jul 2006, Carl Fink wrote:
> I'm seeing the lookup failure reported in this bug, using 3.0.3-2-1.
Bad news. Can you give me more information about this issue, because
I cannot reproduce it here.
> Ralf Hildebrandt says on the bugs page that it's fixed in 3.0.3-6.
> Well and good, but that version isn't even in Sid. Can the bug
> really be marked fixed when it isn't actually fixed in any Debian
> distro?
Please note, that 3.0.3-2-1 is in etch and sid, which is _newer_ than
3.0.3-6 (yes, the numbering is very ugly, but upstream stepped from
3.0.3 to 3.0.3-2 (upstream version!), so 3.0.3-2-1 is the new Debian
version). This numbering is correct in the sense of Debian version
numbering:
$ dpkg --compare-versions 3.0.3-6 lt 3.0.3-2-1 ; echo $?
0
So 3.0.3-6 is less than 3.0.3-2-1
> That report was back in February, so it can't be a build problem,
> can it?
I don't have any idea what happens there. I use privoxy every day on
several machines (i686 and amd64) and never got the message "cannot
resolve domain". I use a local caching DNS on the amd64 machine,
while all others use nameservers on other machines.
If you can reproduce this problem, maybe it's possible to do some
sniffering to find out what happens between your privoxy and the
nameserver (maybe you really have a DNS problem?).
Ciao
Roland
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
