The current implementation of the bzr.eclass doesn't handle the http_proxy correctly (is being set in make.conf). Reproducible: Always Steps to Reproduce: Example ("proxy.dep.domain.tld:3128" has been replaced for obvious reasons) : Fourrier ~ # emerge grub * Last emerge --sync was 47d 22h 46m 45s ago. Calculating dependencies... done! >>> Verifying ebuild manifests >>> Emerging (1 of 1) sys-boot/grub-9999 * checking ebuild checksums ;-) ... [ ok ] * checking auxfile checksums ;-) ... [ ok ] * checking miscfile checksums ;-) ... [ ok ] * CPV: sys-boot/grub-9999 * REPO: gentoo * USE: amd64 elibc_glibc kernel_linux multilib multislot truetype userland_GNU >>> Unpacking source... * bzr fetch start --> * repository: http://bzr.savannah.gnu.org/r/grub/trunk/grub => /usr/portage/distfiles/bzr-src/grub bzr: ERROR: Invalid url supplied to transport: "proxy.dep.domain.tld:3128": No host component * ERROR: sys-boot/grub-9999 failed: * bzr.eclass: can't branch from http://bzr.savannah.gnu.org/r/grub/trunk/grub. * * Call stack: * ebuild.sh, line 48: Called src_unpack * environment, line 3464: Called bzr_src_unpack * environment, line 705: Called bzr_fetch * environment, line 672: Called bzr_initial_fetch 'http://bzr.savannah.gnu.org/r/grub/trunk/grub' '/usr/portage/distfiles/bzr-src/grub' * environment, line 692: Called die * The specific snippet of code: * ${EBZR_FETCH_CMD} ${EBZR_OPTIONS} "${repository}" "${branch_dir}" || die "${EBZR}: can't branch from ${repository}." * * If you need support, post the output of 'emerge --info =sys-boot/grub-9999', * the complete build log and the output of 'emerge -pqv =sys-boot/grub-9999'. * The complete build log is located at '/var/lib/entropy/logs/sys-boot:grub-9999:20100913-132653.log'. * The ebuild environment file is located at '/dev/shm/portage/sys-boot/grub-9999/temp/environment'. * S: '/dev/shm/portage/sys-boot/grub-9999/work/grub-9999' >>> Failed to emerge sys-boot/grub-9999, Log file: Actual Results: The only workaround is to disable the proxy, in my case, it works because the proxy isn't mandatory, otherwise this means the bzr ebuilds cannot work behind a proxy-only connection.
Ok, does youe http_proxy string work on the command line with e.g. w3m/wget/links/... or bzr itself?
(In reply to comment #1) > Ok, does youe http_proxy string work on the command line with e.g. > w3m/wget/links/... or bzr itself? Sorry, I didn't see that reply come through, the answer is yes. The proxy setting is valid and I have been using it with most of the other tools/means of emerging packages (and it's also used for browsers and manually with wget). So I know there isn't a typo in the proxy setting. I checked the manpage (iirc) and there was no mention on handling proxies.
As https://bugs.launchpad.net/bzr/+bug/330823 mentions: use http://<proxy-server>:80/ which is the way bzr interprets those variables. So I'd say this is UPSTREAM.
