Bug 159165

Summary:	summary of orphan files after an unmerge process
Product:	Portage Development	Reporter:	Fabio Rossi <rossi.f>
Component:	Core - Interface (emerge)	Assignee:	Portage team <dev-portage>
Status:	RESOLVED DUPLICATE
Severity:	enhancement	CC:	bug, gengor, gtbgs, q, zlin
Priority:	High
Version:	unspecified
Hardware:	All
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---
Bug Depends on:
Bug Blocks:	193766

Description Fabio Rossi 2006-12-26 15:23:08 UTC

It'd be great to find a (cumulative) summary, at the end of unmerge actions called with 'emerge -C', with a list of orphan files not removed during the process.

In this way it'd be possible to find immediately which are the orphan files on the filesystem.

What do you think about?

Comment 1 Zac Medico gentoo-dev

2006-12-26 15:30:39 UTC

Now that bug 8423 has been fixed (in portage-2.1.2) orphan files will be much less of an issue.  The only remaining issue is bug 16162, which is only an issue for files that have changed mtime or md5sum.

Comment 2 Fabio Rossi 2006-12-26 16:09:29 UTC

I guess that this bug will be closed after the bug #16162 :-) In the meantime it could be used as a summary for bugs #8423 and #16162.

As I have understood portage-2.1.2 will contain a lot of very interesting changes. Thanks Zac for your hard work!!!

Comment 3 Zac Medico gentoo-dev

2006-12-28 17:36:45 UTC

I suppose we might be able to use the elog framework for this but I'm not sure if that would be appropriate.

Comment 4 Fabio Rossi 2006-12-29 01:23:27 UTC

The summary has to be shown only one time at the end of unemerge action(s) (not during the unmerge phase of an upgrade), just like a config file management message.

The elog framework is suitable for automated processes. In our case the user calls explicitly "emerge -C" and for this reason it can see the notice. So, IMHO I don't think the elog framework is appropriate in this case.

Comment 5 Bo Ørsted Andresen (RETIRED) gentoo-dev

2006-12-29 13:36:57 UTC

Personally I'd be quite interested in having portage store log files with lists of files orphaned due to mtime, config protect or whatever with the package they used to belong to somewhere.

Comment 6 Marius Mauch (RETIRED) gentoo-dev

2007-01-11 13:40:02 UTC

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

Comment 7 Marius Mauch (RETIRED) gentoo-dev

2007-01-12 06:27:04 UTC

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

Comment 8 Zac Medico gentoo-dev

2007-06-15 03:35:26 UTC

In portage-2.1.3_rc1 we have FEATURES=unmerge-orphans (enabled by default) which solves bug #134620 and should result in much fewer orphans being left after unmerge.  With this new feature, the only thing that will ever be left behind is a  file that is protected by CONFIG_PROTECT and has been modified since installation.

Comment 9 niogic 2009-04-12 17:19:41 UTC

(In reply to comment #8)
>CONFIG_PROTECT

Interested in listing those files! If not portage, a tool script.

Comment 10 Alexander Berntsen (RETIRED) gentoo-dev

2016-02-03 13:28:34 UTC

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

Comment 11 Zac Medico gentoo-dev

2018-02-02 00:53:42 UTC

(In reply to niogic from comment #9)
> (In reply to comment #8)
> >CONFIG_PROTECT
> 
> Interested in listing those files! If not portage, a tool script.

Maybe use the qfile --orphans option.

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