When I run "emerge --update system" I see the following: Calculating system dependencies ...done! >>> emerge (1 of 2) sys-devel/binutils-2.14.90.0.7-r4 to / >>> Downloading http://mirrors.tds.net/gentoo/distfiles/binutils-2.14.90.0.7.tar.bz2 --06:46:45-- http://mirrors.tds.net/gentoo/distfiles/binutils-2.14.90.0.7.tar.bz2 => `/usr/portage/distfiles/binutils-2.14.90.0.7.tar.bz2' Resolving mirrors.tds.net... 216.170.230.33 Connecting to mirrors.tds.net[216.170.230.33]:80... connected. HTTP request sent, awaiting response... 200 OK Length: 10,575,077 [application/x-bzip2] 59% [==================================> ] 6,313,005 370.12K/s ETA 00:11 07:02:01 (384.00 KB/s) - Read error at byte 6313005/10575077 (Connection timed out). Retrying. --07:02:02-- http://mirrors.tds.net/gentoo/distfiles/binutils-2.14.90.0.7.tar.bz2 (try: 2) => `/usr/portage/distfiles/binutils-2.14.90.0.7.tar.bz2' Connecting to mirrors.tds.net[216.170.230.33]:80... connected. HTTP request sent, awaiting response... ============================================================================= This has happened repeatedly even at different mirrors. Prior to this, glibc 2.3.2-r9 was emerged with the command: emerge --update system Reproducible: Always Steps to Reproduce: 1. 2. 3. Expected Results: downloaded the entire binutils-2.14.90.0.7.tar.bz2 and finish emerge
finally got it to dowload and finish at http://mirror.tucdemonic.org/gentoo/ with no idea of reason for previous problem at 3 other mirrors
I can't recreate this.. could have been a network issue at the time?? If it happens again, please re-open this bug and list all of the mirrors you tried. btw, 370K/s, nice speed! Cheers!
