499682 – Pulls in gcc:4.7 on -u world without any reason

Bug 499682 - Pulls in gcc:4.7 on -u world without any reason

Summary: Pulls in gcc:4.7 on -u world without any reason

Status:	RESOLVED INVALID

Alias:	None

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

Importance:	Normal normal (vote)
Assignee:	Portage team

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2014-01-29 13:58 UTC by Cedric Sodhi
Modified:	2014-01-29 14:12 UTC (History)
CC List:	1 user (show)

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

Attachments
emerge --info (info,4.20 KB, text/plain) 2014-01-29 13:59 UTC, Cedric Sodhi	Details
View All 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 Cedric Sodhi 2014-01-29 13:58:22 UTC

portage-2.2.7, trying to find out *why* exactly emerge wants to pull something in turns out more difficult than I thought - perhaps this could be improved?

In this particular case

emerge -u world

will try to slot install and older version of gcc

[ebuild  NS    ] sys-devel/gcc-4.7.3-r1:4.7 [4.8.2:4.8]

for no apparent reason, whatsoever. It's neither a dependency of any other package, nor is it selected.

Comment 1 Cedric Sodhi 2014-01-29 13:59:56 UTC

Created attachment 369062 [details]
emerge --info

Comment 2 Cedric Sodhi 2014-01-29 14:12:24 UTC

Explanation: gcc:4.8 is unstable and the current config does not permit ustable, so the most stable version is emerged. But since gcc is slotted, 4.8 is not removed and this is technically no downgrade. I guess I was led away from the actual reason by this not being marked as a downgrade.