Mark Knecht wrote: > On Jan 29, 2008 4:21 PM, Neil Bothwick <[EMAIL PROTECTED]> wrote: >> On Tue, 29 Jan 2008 16:16:25 -0800, Mark Knecht wrote: >> >>> First step would be eix-sync which is >>> failing with only a message >>> >>> problems running time emerge --sync >> Run emerge --sync directly so you can see the actual error message. >> >> >> -- >> Neil Bothwick > > Hi Neil, > Thanks. It looks like the following. I guess I'll keep trying. What > I'm not understanding is why my other machines don't have a problem > but this one does. Possibly because it has a bigger update to do? > > Maybe I should run my own portage server here for our 6 home machines? > > - Mark > > dev-php/PEAR-HTML_Common/PEAR-HTML_Common-1.2.4.ebuild > dev-php/PEAR-HTML_Common2/ChangeLog > dev-php/PEAR-HTML_Common2/Manifest > dev-php/PEAR-HTML_Common2/PEAR-HTML_Common2-2.0.0_beta1.ebuild > dev-php/PEAR-HTML_Javascript/ChangeLog > dev-php/PEAR-HTML_Javascript/Manifest > io timeout after 180 seconds -- exiting > rsync error: timeout in data send/receive (code 30) at io.c(165) > [receiver=2.6.9] > rsync: connection unexpectedly closed (3195946 bytes received so far) > [generator] > rsync error: error in rsync protocol data stream (code 12) at > io.c(458) [generator=2.6.9] >>>> Retrying... > > >>>> Starting retry 1 of 3 with rsync://64.127.121.98/gentoo-portage >>>> Checking server timestamp ... > timed out > rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at > rsync.c(276) [receiver=2.6.9] >>>> Retrying... > > >>>> Starting retry 2 of 3 with rsync://140.211.166.165/gentoo-portage >>>> Checking server timestamp ... > rsync: connection unexpectedly closed (0 bytes received so far) [receiver] > rsync error: error in rsync protocol data stream (code 12) at > io.c(458) [receiver=2.6.9] >>>> Retrying... > > >>>> Starting retry 3 of 3 with rsync://134.68.220.73/gentoo-portage >>>> Checking server timestamp ... > timed out > rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at > rsync.c(276) [receiver=2.6.9] > > !!! Rsync has not successfully finished. It is recommended that you keep > !!! trying or that you use the 'emerge-webrsync' option if you are unable > !!! to use rsync due to firewall or other restrictions. This should be a > !!! temporary problem unless complications exist with your network > !!! (and possibly your system's filesystem) configuration. > > Sector9 ~ #
Have you tried a different mirror? It looks like the mirror you are using is having a problem based on the rsync errors. -- gentoo-user@lists.gentoo.org mailing list
