338000 – --depclean is satisfied with masked ruby:1.9 whilst merge is not

Bug 338000 - --depclean is satisfied with masked ruby:1.9 whilst merge is not

Summary: --depclean is satisfied with masked ruby:1.9 whilst merge is not

Status:	RESOLVED DUPLICATE of bug 332719

Alias:	None

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

Importance:	High minor (vote)
Assignee:	Portage team

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2010-09-19 08:19 UTC by Michał Górny
Modified:	2010-09-19 09:02 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 Michał Górny archtester

2010-09-19 08:19:32 UTC

I've got a single packages RDEPENDing on dev-lang/ruby (without SLOT specification), and ruby:1.9 installed (which was masked afterwards).

When running 'emerge -uD @world', it insists that ruby:1.8 needs to be installed for the particular ruby package dependency to be fulfilled. However, afterwards 'emerge --depclean' insists on removing ruby:1.8.

I guess portage should be consistent in dependency graph calculations, and either do not remove any of the ruby versions at all or remove masked :1.9.

Comment 1 Zac Medico gentoo-dev

2010-09-19 08:24:04 UTC

This is very similar to bug 332719. Is it producible with latest portage?

Comment 2 Michał Górny archtester

2010-09-19 09:02:38 UTC

With today's it is indeed not. Sorry for the noise then.

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