Hi, I don't agree with adding: export http_proxy = http://127.0.9.1:9
on top of debian/rules. The reason is that, by doing this, you are hiding problems. If a python package downloads something using pip or anything else, it most likely means that you forgot a build-depends. This show in this very bug (eg: #690575). So remove it, and if during the build process something tries to download a python package, then you need to simply fix your build-depends. I'm open to discussions on this very subject though. By the way, I have just added the use of update-alternatives in the package so that it provides /usr/bin/coverage for those (upstream code or users) who needs it. After this, I think the package is up to shape for an upload: I tested it against some of the upstream code I maintain, and it generated correctly the expected coverage report. Please get in touch so that I can (hopefully, soon, if we agree) sponsor the upload of this package in Sid. Cheers, Thomas Goirand (zigo) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
