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 <gentoo-amd64+bounces-8784-garchives=archives.gentoo.org@gentoo.org>) id 1ImX3j-0003ao-Ll for garchives@archives.gentoo.org; Mon, 29 Oct 2007 16:01:48 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.14.1/8.14.0) with SMTP id l9TFwvc4001067; Mon, 29 Oct 2007 15:58:57 GMT Received: from an-out-0708.google.com (an-out-0708.google.com [209.85.132.251]) by robin.gentoo.org (8.14.1/8.14.0) with ESMTP id l9TFwtiG001058 for <gentoo-amd64@lists.gentoo.org>; Mon, 29 Oct 2007 15:58:56 GMT Received: by an-out-0708.google.com with SMTP id c38so191991ana for <gentoo-amd64@lists.gentoo.org>; Mon, 29 Oct 2007 08:58:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; bh=8mD1xczvjLUUyPYqWUaL1FOaWWjiJvL/iBX0PPwPIPU=; b=rc1Voxz7V9vJR06/WHLTSfZ6OI7HxCKGTsvELCJawvWosVJqiQZN46wmOqRT5hBDqND21Dm6TXIc57IIzA9yl8FeCk7dMdhzmm7WUGAfd/gPH01e15AcJosg51Ke9yxWgm/cxJxPggMyVELwZDqksykpid85BhYGJiY9GWz2jz4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=rhcp0udYz6Qem6lNq7Smym9YtBZma8pqFntP+yKMNvZiRcnnXSrNKYRm7xmh9+mU9kOLRQHvQgAIjTpY9j85kQ+GyT8gBE/4IS7smRTwLUq81KX0gjRFAKohICReUOgzq/sE1IyUkcHop1KJEhu0B3QJVSQMU5b06vpR4tD/2lY= Received: by 10.142.165.9 with SMTP id n9mr1353756wfe.1193673534529; Mon, 29 Oct 2007 08:58:54 -0700 (PDT) Received: by 10.142.83.15 with HTTP; Mon, 29 Oct 2007 08:58:54 -0700 (PDT) Message-ID: <236d8ce90710290858w55097afnfa11dc01564f5604@mail.gmail.com> Date: Mon, 29 Oct 2007 21:58:54 +0600 From: "Stein Burzum" <stein.burzum@gmail.com> To: gentoo-amd64@lists.gentoo.org Subject: Re: [gentoo-amd64] emerge --sync failed In-Reply-To: <200710291508.41393.gentoo@appjaws.plus.com> Precedence: bulk List-Post: <mailto:gentoo-amd64@lists.gentoo.org> List-Help: <mailto:gentoo-amd64+help@gentoo.org> List-Unsubscribe: <mailto:gentoo-amd64+unsubscribe@gentoo.org> List-Subscribe: <mailto:gentoo-amd64+subscribe@gentoo.org> List-Id: Gentoo Linux mail <gentoo-amd64.gentoo.org> X-BeenThere: gentoo-amd64@gentoo.org Reply-to: gentoo-amd64@lists.gentoo.org MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_21528_16990682.1193673534509" References: <200710291508.41393.gentoo@appjaws.plus.com> X-Archives-Salt: 8ca42078-47f8-47dd-8d3d-cd786e773aea X-Archives-Hash: d9fc35becc9ae2fdc63629f24ff91101 ------=_Part_21528_16990682.1193673534509 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline On 10/29/07, Paul Stear <gentoo@appjaws.plus.com> wrote: > > Hi I sent this message the other day and updated my mirror list. Today I > just keep getting timed out when using emerge --sync. > Any help please. > > # emerge --sync > >>> Starting rsync 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 1 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] > >>> Retrying... > > > >>> Starting retry 2 of 3 with rsync://134.68.220.74/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://134.68.220.73/gentoo-portage > >>> Checking server timestamp ... > timed out > rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at rsync.c(244) > [receiver=2.6.9] > > Thanks Paul > > 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 > -- > This message has been sent using kmail with gentoo linux > -- > gentoo-amd64@gentoo.org mailing list > > > -- > This email has been verified as Virus free > Virus Protection and more available at http://www.plus.net > > ------------------------------------------------------- > > -- > This message has been sent using kmail with gentoo linux > -- > gentoo-amd64@gentoo.org mailing list > > Rsync-server needs direct connection to your computer. According to your `timed out', are you behind firewall/NAT or something like this? -- Free as in `freedom', not as beer. ------=_Part_21528_16990682.1193673534509 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline <br><br><div><span class="gmail_quote">On 10/29/07, <b class="gmail_sendername">Paul Stear</b> <<a href="mailto:gentoo@appjaws.plus.com">gentoo@appjaws.plus.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> Hi I sent this message the other day and updated my mirror list. Today I<br>just keep getting timed out when using emerge --sync.<br>Any help please.<br><br># emerge --sync<br>>>> Starting rsync with rsync://64.127.121.98/gentoo-portage... <br>>>> Checking server timestamp ...<br>timed out<br>rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at rsync.c(244)<br>[receiver=2.6.9]<br>>>> Retrying...<br><br><br>>>> Starting retry 1 of 3 with rsync://140.211.166.165/gentoo-portage <br>>>> Checking server timestamp ...<br>timed out<br>rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at rsync.c(244)<br>[receiver=2.6.9]<br>>>> Retrying...<br><br><br>>>> Starting retry 2 of 3 with rsync://134.68.220.74/gentoo-portage <br>>>> Checking server timestamp ...<br>timed out<br>rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at rsync.c(244)<br>[receiver=2.6.9]<br>>>> Retrying...<br><br><br>>>> Starting retry 3 of 3 with rsync://134.68.220.73/gentoo-portage <br>>>> Checking server timestamp ...<br>timed out<br>rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at rsync.c(244)<br>[receiver=2.6.9]<br><br>Thanks Paul<br><br>Hi all,<br>I'm sorry if this has been covered but I have had trouble with my mail. <br>I use the command eix-sync && emerge -auvtDN world && prelink -aqR to<br>update my system. However, since Friday I am getting the following<br>output:-<br>* Removing old portage-cache in /var/cache/edb/dep ... {ok ] <br> * Running emerge --sync ...<br> * Problems running time emerge --sync [ !! ]<br> * emerge --sync failed<br><br>Has anybody any ideas as to what is causing this and how to solve it?<br>Thanks <br>Paul<br>--<br>This message has been sent using kmail with gentoo linux<br>--<br><a href="mailto:gentoo-amd64@gentoo.org">gentoo-amd64@gentoo.org</a> mailing list<br><br><br>--<br>This email has been verified as Virus free <br>Virus Protection and more available at <a href="http://www.plus.net">http://www.plus.net</a><br><br>-------------------------------------------------------<br><br>--<br>This message has been sent using kmail with gentoo linux <br>--<br><a href="mailto:gentoo-amd64@gentoo.org">gentoo-amd64@gentoo.org</a> mailing list<br><br></blockquote></div><br>Rsync-server needs direct connection to your computer. According to your `timed out', are you behind firewall/NAT or something like this? <br clear="all"><br>-- <br>Free as in `freedom', not as beer. ------=_Part_21528_16990682.1193673534509-- -- gentoo-amd64@gentoo.org mailing list