During the build for xen-tools 4.1.0 the makefile will attempt to pull a tarball from xensource.com as follows. This will fail if the build is being done in an air gapped network or standalone pc: make[4]: Entering directory `/var/tmp/portage/app-emulation/xen-tools-4.1.0-r1/work/xen-4.1.0/tools/firmware' make -C etherboot all make[5]: Entering directory `/var/tmp/portage/app-emulation/xen-tools-4.1.0-r1/work/xen-4.1.0/tools/firmware/etherboot' make NO_WERROR=1 eb-roms.h.new make[6]: Entering directory `/var/tmp/portage/app-emulation/xen-tools-4.1.0-r1/work/xen-4.1.0/tools/firmware/etherboot' if ! wget -O _ipxe.tar.gz http://xenbits.xensource.com/xen-extfiles/ipxe-git-v1.0.0.tar.gz; then \ git clone git://git.ipxe.org/ipxe.git ipxe.git; \ (cd ipxe.git && git archive --format=tar --prefix=ipxe/ \ v1.0.0 | gzip >../_ipxe.tar.gz); \ rm -rf ipxe.git; \ fi --2011-05-05 13:37:00-- http://xenbits.xensource.com/xen-extfiles/ipxe-git-v1.0.0.tar.gz USE FLAGS: [ebuild U ] app-emulation/xen-tools-4.1.0-r1 [4.0.0] USE="acm api doc flask hvm -custom-cflags -debug -ioemu -pygrub -screen" 0 kB
1) Please attach the entire build log. 2) Please post your `emerge --info' output too.
Created attachment 272969 [details] emerge --info
Created attachment 272971 [details] emerge log
This doesn't look like a bug. The source of the package does seek xensource as a matter of course. Have not heard of an air gapped network. If the emerge manages to fetch the source initially, what stops it from fetching from xensource during an emerge?
For security reasons, some networks are set up standalone. They only allow the transfer of files to the outside world via physical transfer of media (and usually some sort of review/approval process). Thus the term "air gapped". All ebuilds that attempt to contact an outside site for additional content will fail as a matter of course.
This was a curious one to fix, but it is. Will be in the tree 'soon'