From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1Iln9L-0001jP-3n for garchives@archives.gentoo.org; Sat, 27 Oct 2007 15:00:31 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.14.1/8.14.0) with SMTP id l9REwBSe023372; Sat, 27 Oct 2007 14:58:11 GMT Received: from ptb-relay02.plus.net (ptb-relay02.plus.net [212.159.14.213]) by robin.gentoo.org (8.14.1/8.14.0) with ESMTP id l9REwATq023359 for ; Sat, 27 Oct 2007 14:58:10 GMT Received: from [212.159.109.207] (helo=[192.168.1.6]) by ptb-relay02.plus.net with esmtp (Exim) id 1Iln74-0005tS-7G for gentoo-amd64@lists.gentoo.org; Sat, 27 Oct 2007 15:58:10 +0100 From: Paul Stear Organization: appjaws To: gentoo-amd64@lists.gentoo.org Subject: Re: [gentoo-amd64] emerge --sync failed Date: Sat, 27 Oct 2007 15:59:19 +0100 User-Agent: KMail/1.9.7 References: <200710271443.03861.gentoo@appjaws.plus.com> <20071027094738.3c73939f@Midori.localhost> In-Reply-To: <20071027094738.3c73939f@Midori.localhost> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-amd64@gentoo.org Reply-to: gentoo-amd64@lists.gentoo.org MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200710271559.19682.gentoo@appjaws.plus.com> X-Archives-Salt: 76e0732b-b7a3-479b-ae74-5225f6462055 X-Archives-Hash: 5c64a29e24d6fc11911b2eab269b1ae4 On Saturday 27 October 2007, Kenneth Prugh wrote: > On Sat, 27 Oct 2007 14:43:03 +0100 > > Paul Stear wrote: > > Hi all, > > I'm sorry if this has been covered but I have had trouble with my > > mail. I use the command eix-sync && emerge -auvtDN world && prelink > > -aqR to update my system. However, since Friday I am getting the > > following output:- > > * Removing old portage-cache in /var/cache/edb/dep ... > > {ok ] > > * Running emerge --sync ... > > * Problems running time emerge --sync > > [ !! ] > > * emerge --sync failed > > > > Has anybody any ideas as to what is causing this and how to solve it? > > Thanks > > Paul > > Not sure, but does `emerge --sync` actually work? That would probably > give a more detailed error than eix does. Hi, this is the error for emerge --sync:- >>> Starting retry 2 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(244) [receiver=2.6.9] >>> Retrying... >>> Starting retry 3 of 3 with rsync://140.211.166.165/gentoo-portage >>> Checking server timestamp ... timed out rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at rsync.c(244) [receiver=2.6.9] So it appears a time out problem. What should I do now? Thanks Paul -- This message has been sent using kmail with gentoo linux -- gentoo-amd64@gentoo.org mailing list