Gentoo Logo
Gentoo Spaceship




Note: Due to technical difficulties, the Archives are currently not up to date. GMANE provides an alternative service for most mailing lists.
c.f. bug 424647
List Archive: gentoo-amd64
Navigation:
Lists: gentoo-amd64: < Prev By Thread Next > < Prev By Date Next >
Headers:
To: gentoo-amd64@g.o
From: Paul Stear <gentoo@...>
Subject: Re: emerge --sync failed
Date: Sun, 28 Oct 2007 10:49:18 +0000
On Saturday 27 October 2007, Beso wrote:
> probably the rsync has changed ip. try one of this servers:
> sync = rsync://rsync.gentoo.org/gentoo-portage
> #sync = rsync://rsync3.it.gentoo.org/gentoo-sources
> #sync = http://www.die.unipd.it/pub/Linux/distributions/gentoo-sources/
> #sync = http://mirror.ing.unibo.it/gentoo/
> the first is the official one, the others should be mirrors. a full
> list of rsync mirrors can be found somewhere on the gentoo site. just
> search for it. the problem with your method is that you don't pass
> through a dns server asking directly for an ip address and this could
> not work anymore when the site you're trying has changed ip. you'd have
> to get again the ip. if you want to use the ip address try searching
> the name with a ping or traceroute or in some dns site like in the
> opendns cache site.
>
> 2007/10/27, Paul Stear <gentoo@...>:
> > On Saturday 27 October 2007, Kenneth Prugh wrote:
> > > On Sat, 27 Oct 2007 14:43:03 +0100
> > >
> > > Paul Stear <gentoo@...> 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@g.o mailing list

Hi,
Thanks. I have used mirrorselect and updated make.conf and it now works.
Paul

-- 
This message has been sent using kmail with gentoo linux
-- 
gentoo-amd64@g.o mailing list


References:
emerge --sync failed
-- Paul Stear
Re: emerge --sync failed
-- Paul Stear
Re: emerge --sync failed
-- Beso
Navigation:
Lists: gentoo-amd64: < Prev By Thread Next > < Prev By Date Next >
Previous by thread:
Re: emerge --sync failed
Next by thread:
unsubscribe
Previous by date:
Re: Load NTLDR from GRUB?
Next by date:
Re: Re: Load NTLDR from GRUB?


Updated Dec 13, 2010

Summary: Archive of the gentoo-amd64 mailing list.

Donate to support our development efforts.

Copyright 2001-2013 Gentoo Foundation, Inc. Questions, Comments? Contact us.