Bug#683908: gpsprune: doesn't properly use $http_proxy

2013-04-20 Thread debian
Thank you for that. That looks good, simpler than using an extra grep. I've not seen those sed options before. One minor suggestion, it might be worth changing: proxyport=$(echo $http_proxy | sed -n 's?http://[^:]\+:\([0-9]\+\)?\1?p') to proxyport=$(echo $http_proxy | sed -n 's?http://[^:]

Bug#683908: gpsprune: doesn't properly use $http_proxy

2012-11-22 Thread debian
I think there are two possibilities here - either the starter script gpsprune doesn't parse the proxy information properly and passes the wrong information to GpsPrune, or the networking stuff used by GpsPrune doesn't take any notice of what's passed in. It would be very useful to know whether

Bug#683908: gpsprune: doesn't properly use $http_proxy

2012-08-05 Thread Marc Lehmann
Package: gpsprune Version: 10-1 Severity: normal gpsprune uses the http_proxy environment variable to access maps, but ignores the port. e.g. http_proxy=http://10.0.0.1:3128 gpsprune after that, gpsprune tries to connect to 10.0.0.1 port 80, i.e. it completely ignores the port, but does us