Bug 57262

Summary:	rsync error during initial emerge sync
Product:	Portage Development	Reporter:	Jacob Levine <bugzilla>
Component:	Tools	Assignee:	Portage team <dev-portage>
Status:	RESOLVED INVALID
Severity:	normal
Priority:	High
Version:	unspecified
Hardware:	x86
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---

Description Jacob Levine 2004-07-16 01:12:31 UTC

I was following the default installation instructions from http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=1&chap=6 and got as far as the "emerge sync" step. This downloaded many packages, and was ultimately successful, but towards the end it encountered an rsync error which caused it to have to retry one download. The output was: 

sys-devel/binutils/binutils-2.12.90[I didn't have a chance to copy the rest of this before the screen scrolled]
rsync: writefd_unbuffered failed to write 4092 bytes: phase "unknown": Connection reset by peer
rsync error: error in rsync protocol data stream (code 12) at io.c(666)
>>> retry ...
rsync error: received SIGUSR1 or SIGINT (code 20) at main.c(886)

Reproducible: Didn't try
Steps to Reproduce:
1. Followed the default installation isntructions from the Gentoo handbook at http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=1&chap=6 
2. Got as far as "emerge sync".
3. This produced the error midway through.

Actual Results:  
rsync encountered an error which caused the portage system to have to restart
one download.

Expected Results:  
No error should have occurred.

As I'm in the middle of an installation I can't include the "emerge info " data,
but I'm installing 2004.1 2.4.25-gentoo kernel on a Celeron 500 from a stage 2
tarball, booted from a minimal LiveCD.

Comment 1 Nicholas Jones (RETIRED) gentoo-dev

2004-09-29 17:50:41 UTC

That's a network failure followed by a control-C.
I don't see anything we can fix.