101204 – emerge does not handle SIGINT (^C) well

Bug 101204 - emerge does not handle SIGINT (^C) well

Summary: emerge does not handle SIGINT (^C) well

Status:	RESOLVED FIXED

Alias:	None

Product:	Portage Development
Classification:	Unclassified
Component:	Core - Interface (emerge) (show other bugs)
Hardware:	All Linux

Importance:	High normal (vote)
Assignee:	Portage team

URL:
Whiteboard:
Keywords:

Duplicates (2):	91200 116434 (view as bug list)
Depends on:
Blocks:

Reported:	2005-08-03 07:32 UTC by LionsPhil
Modified:	2006-07-25 23:14 UTC (History)
CC List:	4 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 LionsPhil 2005-08-03 07:32:32 UTC

Emerge doesn't appear to catch ^C / SIGINT during many operations and close down 
cleanly, instead treating it as if an error had occoured. This may lead to 
misleading error messages or debugging information being displayed.

Reproducible: Always
Steps to Reproduce:
1. Start an emerge operation. emerge -puDv world is a good one as it takes a few 
seconds.
2. Hit Control-C before it finishes.
Actual Results:  
A variety of interesting yet false error messages about how broken portage is 
and how to recover it (e.g. "!!! Failed to complete portage imports..."), and/or 
a Python stack trace.

Expected Results:  
Catch the signal and close cleanly, or at least close without incorrect output.

n/a

Comment 1 Zac Medico gentoo-dev

2005-10-18 01:50:57 UTC

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

Comment 2 Zac Medico gentoo-dev

2005-12-22 16:54:05 UTC

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

Comment 3 Zac Medico gentoo-dev

2006-07-25 23:14:07 UTC

This has been fixed for some time (at least >=2.1).