Bug 165780 – emerge disagrees with etc-update about ._cfgxxx_Y~ (note ~_

• Status: RESOLVED FIXED
• Product: Portage Development

[Description Allan Gottlieb 2007-02-07 15:58:23 UTC]

emerge depclean considers _cfgxxx_*~ a configuration update while
etc-update doesn't.  So one gets

ajglap gottlieb # emerge --depclean --ask;  etc-update

*** WARNING ***  Depclean may break link level dependencies.  Thus, it is

[std msgs from --depclean snipped]

Number removed:       0

 * GNU info directory index is up-to-date.
 * IMPORTANT: 1 config files in /etc need updating.
 * Type emerge --help config to learn how to update config files.

Scanning Configuration files...
Exiting: Nothing left to do; exiting. :)


Reproducible: Always

Steps to Reproduce:
1. touch /etc/._cfgxxxx_dd~
2. emerge --depclean; etc-update
3.

Actual Results:  
Shown in description

Expected Results:  
Probably etc-update should note the ._cfg????_*~
If not --depclean shouldn't either.
That is they should agree

[Comment 1 Harald van Dijk (RETIRED) 2007-02-07 16:47:41 UTC]

This has nothing to do with --depclean specifically; portage always looks for configuration updates the same way. Still, yeah, it and etc-update should agree.

[Comment 2 Simon Stelling (RETIRED) 2007-02-07 18:53:11 UTC]

I suggest you adjust portage instead of etc-update; dispatch-conf and conf-update behave the same way

[Comment 3 Zac Medico 2007-02-07 21:20:37 UTC]

In svn r5914 everything consistently filters '.*~' and '.*.bak'.

[Comment 4 Zac Medico 2007-02-08 05:30:19 UTC]

This has been released on 2.1.2-r9.