Your message dated Fri, 28 Nov 2025 15:51:25 -0500
with message-id
<caaajcma9pdnzokkesqq4r584czub8ebe0nhbiayqzx0ts2c...@mail.gmail.com>
and subject line closing old libproxy bugs
has caused the Debian Bug report #644373,
regarding libproxy0 0.3.1-3 doesn't work with automatic proxy configuration
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.)
--
644373: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=644373
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: libproxy0
Version: 0.3.1-3
Severity: important
Support for the 'Automatic proxy configuration' mode (from
gnome-network-properties) seems to be broken after upgrading libproxy
from version 0.3.1-2.
Instead of returning the list of proxies for a given URL, it just
returns 'direct://'
I'm attaching a simple test case.
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 3.0.0-1-686-pae (SMP w/2 CPU cores)
Locale: LANG=pt_PT, LC_CTYPE=pt_PT (charmap=UTF-8) (ignored: LC_ALL set to
pt_PT.UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages libproxy0 depends on:
ii libc6 2.13-21
Versions of packages libproxy0 recommends:
ii libmozjs6d 6.0.2-1
ii libwebkitgtk-1.0-0 1.4.2-2
libproxy0 suggests no packages.
-- no debconf information
/*
gcc -o test test.c -lproxy
*/
#include <stdio.h>
#include <proxy.h>
int main (void)
{
char *url = "http://www.debian.org/";;
char **p;
pxProxyFactory *factory;
factory = px_proxy_factory_new ();
p = px_proxy_factory_get_proxies (factory, url);
for (; *p != NULL; p++)
{
puts(*p);
}
return 0;
}
--- End Message ---
--- Begin Message ---
There have been many changes to Debian since this bug was originally
reported. If you are still experiencing this issue with Debian 13 (or
with Debian 12 or Testing or Unstable), please report a new bug.
Thank you,
Jeremy Bícha
--- End Message ---
