16583 – Portage updates cache even if sync fails

Bug 16583 - Portage updates cache even if sync fails

Summary: Portage updates cache even if sync fails

Status:	RESOLVED FIXED

Alias:	None

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

Importance:	High enhancement (vote)
Assignee:	Nicholas Jones (RETIRED)

URL:
Whiteboard:
Keywords:

Duplicates (1):	17008 (view as bug list)
Depends on:
Blocks:

Reported:	2003-02-28 15:23 UTC by eric sammer
Modified:	2011-10-30 22:18 UTC (History)
CC List:	2 users (show)

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 eric sammer 2003-02-28 15:23:35 UTC

When performing a sync, emerge will update (or rebuild) the cache even if the
rsync connection to the server fails. This produces wasted time and resource
usage (mainly disk io). The best example is if the connection to the rsync
server is dropped due to max connections which is common enough with some
servers to make it annoying.

Reproducible: Always
Steps to Reproduce:
1. emerge sync and connect to a busy server
2. wait forever
Actual Results:  
Portage will update the cache unconditionally.

Expected Results:  
Portage should skip the cache update if no connection to the server can be made
unless there is a reason to do so (i.e. update failure counts or note mirror usage).

Comment 1 SpanKY gentoo-dev

2003-03-07 08:14:36 UTC

*** Bug 17008 has been marked as a duplicate of this bug. ***

Comment 2 Nicholas Jones (RETIRED) gentoo-dev

2003-03-11 01:41:22 UTC

Fixed in cvs for 2.0.47-r9