| 1 |
I am still running into the same problem since a couple of days ago. I |
| 2 |
tried both |
| 3 |
|
| 4 |
SYNC="rsync://rsync.gentoo.org/gentoo-portage" |
| 5 |
SYNC="rsync://rsync.namerica.gentoo.org/gentoo-portage" |
| 6 |
|
| 7 |
Is anyone having issues with syncing the portage tree? |
| 8 |
|
| 9 |
Thanks, |
| 10 |
|
| 11 |
-- |
| 12 |
Valmor |
| 13 |
|
| 14 |
|
| 15 |
-> emerge --sync |
| 16 |
>>> Starting rsync with rsync://88.198.83.250/gentoo-portage... |
| 17 |
>>> Checking server timestamp ... |
| 18 |
timed out |
| 19 |
rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at |
| 20 |
rsync.c(544) [receiver=3.0.6] |
| 21 |
>>> Retrying... |
| 22 |
|
| 23 |
|
| 24 |
>>> Starting retry 1 of 3 with rsync://88.198.83.249/gentoo-portage |
| 25 |
>>> Checking server timestamp ... |
| 26 |
timed out |
| 27 |
rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at |
| 28 |
rsync.c(544) [receiver=3.0.6] |
| 29 |
>>> Retrying... |
| 30 |
|
| 31 |
|
| 32 |
>>> Starting retry 2 of 3 with rsync://134.68.240.59/gentoo-portage |
| 33 |
>>> Checking server timestamp ... |
| 34 |
timed out |
| 35 |
rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at |
| 36 |
rsync.c(544) [receiver=3.0.6] |
| 37 |
>>> Retrying... |
| 38 |
|
| 39 |
|
| 40 |
>>> Starting retry 3 of 3 with rsync://134.68.240.58/gentoo-portage |
| 41 |
>>> Checking server timestamp ... |
| 42 |
timed out |
| 43 |
rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at |
| 44 |
rsync.c(544) [receiver=3.0.6] |
| 45 |
>>> Exceeded PORTAGE_RSYNC_RETRIES: 3 |
| 46 |
|
| 47 |
|
| 48 |
|
| 49 |
Alejandro Pino Oreamuno wrote: |
| 50 |
> same problem here with 134.68.240.59 , 88.198.83.249 , 88.198.83.250 , |
| 51 |
> 140.211.166.189 |
| 52 |
> |
| 53 |
> |
| 54 |
> Alejandro |
Archives