| 1 |
On Saturday 27 October 2007, Kenneth Prugh wrote: |
| 2 |
> On Sat, 27 Oct 2007 14:43:03 +0100 |
| 3 |
> |
| 4 |
> Paul Stear <gentoo@××××××××××××.com> wrote: |
| 5 |
> > Hi all, |
| 6 |
> > I'm sorry if this has been covered but I have had trouble with my |
| 7 |
> > mail. I use the command eix-sync && emerge -auvtDN world && prelink |
| 8 |
> > -aqR to update my system. However, since Friday I am getting the |
| 9 |
> > following output:- |
| 10 |
> > * Removing old portage-cache in /var/cache/edb/dep ... |
| 11 |
> > {ok ] |
| 12 |
> > * Running emerge --sync ... |
| 13 |
> > * Problems running time emerge --sync |
| 14 |
> > [ !! ] |
| 15 |
> > * emerge --sync failed |
| 16 |
> > |
| 17 |
> > Has anybody any ideas as to what is causing this and how to solve it? |
| 18 |
> > Thanks |
| 19 |
> > Paul |
| 20 |
> |
| 21 |
> Not sure, but does `emerge --sync` actually work? That would probably |
| 22 |
> give a more detailed error than eix does. |
| 23 |
|
| 24 |
Hi, this is the error for emerge --sync:- |
| 25 |
>>> Starting retry 2 of 3 with rsync://64.127.121.98/gentoo-portage |
| 26 |
>>> Checking server timestamp ... |
| 27 |
timed out |
| 28 |
rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at rsync.c(244) |
| 29 |
[receiver=2.6.9] |
| 30 |
>>> Retrying... |
| 31 |
|
| 32 |
|
| 33 |
>>> Starting retry 3 of 3 with rsync://140.211.166.165/gentoo-portage |
| 34 |
>>> Checking server timestamp ... |
| 35 |
timed out |
| 36 |
rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at rsync.c(244) |
| 37 |
[receiver=2.6.9] |
| 38 |
|
| 39 |
So it appears a time out problem. What should I do now? |
| 40 |
Thanks |
| 41 |
Paul |
| 42 |
-- |
| 43 |
This message has been sent using kmail with gentoo linux |
| 44 |
-- |
| 45 |
gentoo-amd64@g.o mailing list |
Archives