Bug 6213 – portage isn't dealling too well with rsync *problems* ... heres an idea

• Product: Portage Development
• Status: RESOLVED FIXED

[Description António Meireles 2002-08-08 12:45:20 UTC]

due, probably, to the (deserverd) increase in popularity of gentoo, the rsync
mirrors are suffering to answer to alll the load. 

One side effect of this is slower updates of the rsyncm mirrors from thr main tree. 

Since recently  portage by default does an emerge --clean at startup if i first
went to a *more* upddated rsync mirror and latter to a slower one (in terms of
syncing to the main cvs tree) the changes that were gotten from the first emerge
will be erased in the second one  (regetting an older tree) . 

I think that an usefull feature could be (like the md5 sigs) have a *timestamp*
signature per file and independent of rsync; this way portage could know if it
is walking *back* in time or not ...

keep the good work 

thanxs in advance, 


just my .2 euros ...

[Comment 1 SpanKY 2002-08-08 14:01:59 UTC]

*** This bug has been marked as a duplicate of 4874 ***

[Comment 2 António Meireles 2002-08-08 14:13:59 UTC]

if you read bellow the third paragraph you'll see that i  'm going far away than
the bug you say i 'm duplicating (i 'm not talking alone  about rsync congestion
- i 'm talking about rsync *time-warps* )... Yep i even *sugest*  a feature
improvement ...

TIA 

[Comment 3 SpanKY 2002-08-08 17:04:24 UTC]

so than this bug report turns into a request for enhancement ;)

[Comment 4 Nicholas Jones (RETIRED) 2002-10-12 15:46:36 UTC]

This isn't really possible with rsync.
There are too many factors to deal with.

And you shouldn't run into this issue if you only rsync once
every hour max. Otherwise you tax the servers.