272240 – On unmerge, gcc should ensure that a valid gcc profile is used

Bug 272240 - On unmerge, gcc should ensure that a valid gcc profile is used

Summary: On unmerge, gcc should ensure that a valid gcc profile is used

Status:	RESOLVED DUPLICATE of bug 130772

Alias:	None

Product:	Gentoo Linux
Classification:	Unclassified
Component:	[OLD] Development (show other bugs)
Hardware:	All Linux

Importance:	High normal (vote)
Assignee:	Gentoo Toolchain Maintainers

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2009-06-02 09:35 UTC by Diego Elio Pettenò (RETIRED)
Modified:	2012-04-09 19:58 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 Diego Elio Pettenò (RETIRED) gentoo-dev

2009-06-02 09:35:58 UTC

Since this just happened to an user over in #gentoo-it it might be worth looking into this.

When removing a GCC version, it would be a nice idea to ensure that the gcc-config profile selected is still valid; this should avoid that removing 4.2 (with --purge or --depclean) puts the system in an unrunnable state.

I guess the issue here would be if one were to remove the highest version, but then they are fscked anyway so I wouldn't even bother to consider it a special case.

Guys?

Comment 1 SpanKY gentoo-dev

2012-04-09 19:58:09 UTC


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