rsync displays an number of errors when rysncing on gentoo

[eial at cs.bgu.ac.il]

On Thu 21 Feb 6:48 2008 Mike Frysinger wrote:
> 
> On Wednesday 20 February 2008, Matt McCutchen wrote:
> > On Wed, 2008-02-20 at 22:17 -0500, Mike Frysinger wrote:
> > > On Wednesday 20 February 2008, Matt McCutchen wrote:
> > > > On Wed, 2008-02-20 at 16:06 -0500, Mike Frysinger wrote:
> > > > > tar jxf snapshot-xxxxxxxx.tar.bz2
> > > > > cd snapshot-xxxxxxxx
> > > > > rsync -av --progress --stats --delete --delete-after \
> > > > > --exclude='/distfiles' --exclude='/packages' --exclude='/local' \
> > > > > . /usr/portage
> > > >
> > > > Mike, I don't share your apparent assumption that emerge-webrsync is
> > > > intrinsically less buggy than rsync.  In any case, I can only answer
> > > > for the behavior of rsync itself, so I need to know the actual rsync
> > > > command line.  The one you gave isn't consistent with the error
> > > > message, in which the absolute path of the missing file doesn't have a
> > > > component of the form "snapshot-xxxxxxxx".
> > >
> > > please re-read the commands i posted.  the rsync is from "."
> > > to "/usr/portage".
> >
> > I don't know what you believe I am overlooking.  Anyway, right now I
> > don't see any way your command could result in the error eial saw, and I
> > don't see the benefit of spending any more effort on this angle unless
> > we get more information from eial.
> 
> the unpacked tarball results in a directory named "portage", 
> not "snapshot-xxxxxxxx". 
> 
> either way, the "emerge-webrsync" is merely a bash shell script.  you can 
> easily find it by googling:
> http://sources.gentoo.org/viewcvs.py/*checkout*/portage/main/trunk/bin/emerge-webrsync
> which contains the rsync command i already pasted.
> 
> the tarball too is a simple thing which can be found via google:
> http://gentoo.osuosl.org/snapshots/portage-20080219.tar.bz2
> and verified via md5:
> http://gentoo.osuosl.org/snapshots/portage-20080219.tar.bz2.md5sum
> 
> the tarball contains no file or link named "180".  either eial has a buggy 
> filesystem/kernel, or rsync screwed something up, or one of the fixes we 
> apply in Gentoo (all of which are from rsync upstream) is causing a problem.  
> it is not the fault of emerge-webrsync.
> -mike
> 

ik, my mistake pre10 is in the tree, I'll emerge it, I've tried with the previous kernel image in which I know for fact that there
was no problems, errors still persists.