Hi, has anyone had this problem with trying to update the database
for portage?
It was doing this a while ago, then it stopped (I don't know why)
now its doing it again..
# emerge --sync
>>> Starting rsync with rsync://91.186.30.235/gentoo-portage...
>>> Checking server timestamp ...
timed out
rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at
rsync.c(543) [Receiver=3.0.7]
>>> Retrying...
>>> Starting retry 1 of 3 with rsync://134.68.240.59/gentoo-portage
>>> Checking server timestamp ...
timed out
rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at
rsync.c(543) [Receiver=3.0.7]
>>> Retrying...
>>> Starting retry 2 of 3 with rsync://88.198.83.250/gentoo-portage
>>> Checking server timestamp ...
timed out
rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at
rsync.c(543) [Receiver=3.0.7]
>>> Retrying...
>>> Starting retry 3 of 3 with rsync://88.198.83.249/gentoo-portage
>>> Checking server timestamp ...
timed out
rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at
rsync.c(543) [Receiver=3.0.7]
>>> Exceeded PORTAGE_RSYNC_RETRIES: 3
06-03-2010, 01:17 PM
Peter Ruskin
problems with rsync (emerge --sync)
On Thursday 03 June 2010 13:43:55 Rod wrote:
> * * *Hi, has anyone had this problem with trying to update the
> database for portage?
>
> * * *It was doing this a while ago, then it stopped (I don't know
> why) now its doing it again..
>
> # emerge --sync
> *>>> Starting rsync with rsync://91.186.30.235/gentoo-portage...
> *>>> Checking server timestamp ...
> timed out
> rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at
> rsync.c(543) [Receiver=3.0.7]
> *>>> Retrying...
It happend a lot here in the UK too. The mirrors seem not up to
snuff.
problems with rsync (emerge --sync)
