** Bug watch added: Debian Bug tracker #604934
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=604934
** Also affects: libproxy (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=604934
Importance: Unknown
Status: Unknown
** Summary changed:
- Please upgrade libproxy
I've built 0.4.6 in my personal PPA. It appears there are a few more
issues though. It seems like there is now a circular dependency issue
with libsoup, as libproxy seems to depend on it now.
--
Please upgrade libproxy to 0.4.0 in Lucid
https://bugs.launchpad.net/bugs/547106
You received this bug
There is one external API change. In < 0.4.0 I had documented that
px_proxy_factory_get_proxies() would never return NULL. In 0.4.0 that
is no longer the case. All though technically ABI is probably unchanged
(its a grey area), I thought it better safe than sorry to bump the
soname. Apps writte
I hope Nathaniel will answer with more detail, but what I seen in code
it's mostly means feature maturity. For example, 0.4 version has very
correct GNOME proxy support, where previous versions where lacking stuff
like authentication, also inner logic has improved.
--
Please upgrade libproxy to 0
the lucid version has been updated to 0.3.2 which is what debian testing
has right now and has been tested, why does the new version has a soname
change if there is no compatibility breakage?
** Changed in: libproxy (Ubuntu)
Importance: Undecided => Wishlist
--
Please upgrade libproxy to 0.4.
To be clear, there is ONE, SMALL API change. In versions >= 0.4.0 the
function px_proxy_factory_get_proxies() may return NULL. Applications
that didn't consider this case should be fixed regardless. Apps that do
consider this case will work on both versions. libproxy 0.4.0 does
include a soname
