13475 – portage updates cache after emerge rsync, even if rsync fails

Bug 13475 - portage updates cache after emerge rsync, even if rsync fails

Summary: portage updates cache after emerge rsync, even if rsync fails

Status:	RESOLVED DUPLICATE of bug 12968

Alias:	None

Product:	Portage Development
Classification:	Unclassified
Component:	Unclassified (show other bugs)
Hardware:	All All

Importance:	High normal (vote)
Assignee:	Gentoo Linux bug wranglers

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2003-01-08 01:32 UTC by Jared H. Hudson (RETIRED)
Modified:	2011-10-30 22:19 UTC (History)
CC List:	0 users

See Also:
Package list:
Runtime testing required:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Jared H. Hudson (RETIRED) gentoo-dev

2003-01-08 01:32:25 UTC

albert root # emerge rsync                                                     
>>> starting rsync with rsync://rsync.gentoo.org/gentoo-portage...
rsync: getaddrinfo: rsync.gentoo.org 873: Temporary failure in name resolution
rsync error: error in socket IO (code 10) at clientserver.c(83)

>>> Updating Portage cache... \

Comment 1 Martin Holzer (RETIRED) gentoo-dev

2003-01-08 05:28:22 UTC


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