I think it's ok to promote ASAP to unblock GNOME, but found some issues worth fixing:
10:13 <@lool> pochu: libproxy-dev should be arch: any; it doesn't make a substantial space saving to have it arch: all and will cause installability issues on slow arches
10:14 <@lool> pochu: python-libproxy is arch: all but has a depends on shlibs:Depends?
10:15 <@lool> No AM_MAINTAINER_MODE and the configure patch is in the wrong order; will cause an autofoo update
I think it's ok to promote ASAP to unblock GNOME, but found some issues worth fixing:
substantial space saving to have it arch: all and will cause
installability issues on slow arches
shlibs: Depends?
order; will cause an autofoo update
10:13 <@lool> pochu: libproxy-dev should be arch: any; it doesn't make a
10:14 <@lool> pochu: python-libproxy is arch: all but has a depends on
10:15 <@lool> No AM_MAINTAINER_MODE and the configure patch is in the wrong
I had read the thread on libproxy on debian-devel@, but I re-read it; the conclusion is that WPAD is disabled by default by gnome-network- properties, but might is enabled by default outside of GNOME. http:// mail.gnome. org/archives/ desktop- devel-list/ 2008-December/ msg00160. html www.mercenary. net/blog/ index.php? /archives/ 42-HOWTO- WPAD.html
Critic of WPAD's flaws: http://