243020 – Allow forced unmerging of packages referenced by sets

Bug 243020 - Allow forced unmerging of packages referenced by sets

Summary: Allow forced unmerging of packages referenced by sets

Status:	CONFIRMED

Alias:	None

Product:	Portage Development
Classification:	Unclassified
Component:	Enhancement/Feature Requests (show other bugs)
Hardware:	All Linux

Importance:	High enhancement (vote)
Assignee:	Portage team

URL:
Whiteboard:
Keywords:

Duplicates (1):	279449 (view as bug list)
Depends on:
Blocks:	144480
	Show dependency tree

Reported:	2008-10-21 09:16 UTC by Manuel Nickschas
Modified:	2010-04-02 12:53 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 Manuel Nickschas 2008-10-21 09:16:34 UTC

It would be very useful to have a way to unmerge packages that are referenced/have been installed by a set. In my particular case, I have two live packages A and B, where A conflicts with an older version of B, and B cannot be updated without A. Easy solution would be to temporarily remove B, emerge A, emerge B. Alas, since both are in a set, I can't do the first step without fiddling in world_sets...

So something like emerge -C --force cat/pkg would be muchly appreciated.

Reproducible: Always

Comment 1 Zac Medico gentoo-dev

2008-10-21 09:21:00 UTC

We already have similar protection via emerge --depclean <atom> so perhaps set protection for --unmerge isn't needed.

Comment 2 Vitaliy V. Osypenko 2009-11-29 01:06:14 UTC

Maybe it would be useful to allow unemerge manually masked packages from sets.

Comment 3 Theo Chatzimichos (RETIRED) archtester

2010-04-02 12:53:53 UTC

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