1 |
Hi, has anyone had this problem with trying to update the database |
2 |
for portage? |
3 |
|
4 |
It was doing this a while ago, then it stopped (I don't know why) |
5 |
now its doing it again.. |
6 |
|
7 |
# emerge --sync |
8 |
>>> Starting rsync with rsync://91.186.30.235/gentoo-portage... |
9 |
>>> Checking server timestamp ... |
10 |
timed out |
11 |
rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at |
12 |
rsync.c(543) [Receiver=3.0.7] |
13 |
>>> Retrying... |
14 |
|
15 |
|
16 |
>>> Starting retry 1 of 3 with rsync://134.68.240.59/gentoo-portage |
17 |
>>> Checking server timestamp ... |
18 |
timed out |
19 |
rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at |
20 |
rsync.c(543) [Receiver=3.0.7] |
21 |
>>> Retrying... |
22 |
|
23 |
|
24 |
>>> Starting retry 2 of 3 with rsync://88.198.83.250/gentoo-portage |
25 |
>>> Checking server timestamp ... |
26 |
timed out |
27 |
rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at |
28 |
rsync.c(543) [Receiver=3.0.7] |
29 |
>>> Retrying... |
30 |
|
31 |
|
32 |
>>> Starting retry 3 of 3 with rsync://88.198.83.249/gentoo-portage |
33 |
>>> Checking server timestamp ... |
34 |
timed out |
35 |
rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at |
36 |
rsync.c(543) [Receiver=3.0.7] |
37 |
>>> Exceeded PORTAGE_RSYNC_RETRIES: 3 |