Bug 187741 – Configuration files are counted incorrectly

• Status: RESOLVED FIXED
• Product: Portage Development

[Description Arfrever Frehtes Taifersar Arahesis (RETIRED) 2007-08-04 17:08:06 UTC]

* GNU info directory index is up-to-date.
 * IMPORTANT: 2 config files in '/etc' need updating.
 * See the CONFIGURATION FILES section of the emerge
 * man page to learn how to update config files.
# emerge -V
Portage 2.2_pre7563 (default-linux/x86/2007.0/desktop, gcc-4.1.2, glibc-2.6-r0, 2.6.22-suspend2-AFTA i686)
#

There is only 1 configuration file in '/etc', which needs updating. I'm attaching a test ebuild.

[Comment 1 Arfrever Frehtes Taifersar Arahesis (RETIRED) 2007-08-04 17:10:27 UTC]

Created attachment 126865 [details]
sys-apps/test/test-1.ebuild

[Comment 2 Zac Medico 2007-08-04 19:46:16 UTC]

Thanks, this is fixed in svn r7564.

[Comment 3 Petteri Räty (RETIRED) 2007-08-04 20:01:40 UTC]

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

[Comment 4 Lars Wendler (Polynomial-C) (RETIRED) 2007-08-06 02:12:22 UTC]

I can reproduce this with portage-2.1.2.11 and portage-2.1.3.3 as well...
So I'd consider this as not fixed.

[Comment 5 Arfrever Frehtes Taifersar Arahesis (RETIRED) 2007-08-06 11:19:34 UTC]

(In reply to comment #4)
> I can reproduce this with portage-2.1.2.11 and portage-2.1.3.3 as well...
> So I'd consider this as not fixed.

It is fixed in >=2.1.3.4 and >=2.2_pre7564.

[Comment 6 Zac Medico 2007-08-10 22:28:34 UTC]

This has been released in 2.1.3.4.

[Comment 7 Carlo Marcelo Arenas Belon 2007-08-14 11:26:13 UTC]

from anyone still experiencing this bug in the stable 2.1.2.x version (2.1.2.11 for amd64) this is also fixed in the 2.1.2 branch of portage but not yet released.

since it is also in 2.1.2, and to prevent dups for this being created I think that dropping the REGRESSION keyword and re-opening this bug would be recommended.

[Comment 8 Carlo Marcelo Arenas Belon 2007-08-14 11:31:45 UTC]

Created attachment 128036 [details, diff]
patch applied to the stable branch of portage with the fix (from svn revision 7565)

could be used in a local overlay for stable users until released in 2.1.2.? or 2.1.3 becomes stable.

tested in amd64, but most likely safe for all archs

[Comment 9 Arfrever Frehtes Taifersar Arahesis (RETIRED) 2007-08-14 15:16:10 UTC]

(In reply to comment #7)
> since it is also in 2.1.2, and to prevent dups for this being created I
> think that dropping the REGRESSION keyword and re-opening this bug would be
> recommended.

It isn't so important to fix it in 2.1.2.9 branch. That branch was created only to allow stabilization of KDE 3.5.7.

[Comment 10 Carlo Marcelo Arenas Belon 2007-08-17 07:21:47 UTC]

my patch comes from branch 2.1.2 (which seems to be accumulating bugfixes and that will be hopefully released sometime as 2.1.2.12), not branch 2.1.2.9

[Comment 11 Arfrever Frehtes Taifersar Arahesis (RETIRED) 2007-08-17 17:32:09 UTC]

(In reply to comment #10)
> my patch comes from branch 2.1.2 (which seems to be accumulating bugfixes
> and that will be hopefully released sometime as 2.1.2.12), not branch
> 2.1.2.9

2.1.2.11 and 2.1.2.12 belong to branch 2.1.2.9.
2.1.2.{[1-9],10} and 2.1.3* belong to branch 2.1.2.

In r7613 Zac Medico backported this fix from branches/2.1.2 r7564.

[Comment 12 Jakub Moc (RETIRED) 2007-08-24 12:47:37 UTC]

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

[Comment 13 Carlo Marcelo Arenas Belon 2007-08-24 18:06:32 UTC]

this is now fixed in portage>=2.1.2.12 (from the 2.1.2.9 branch) and marked stable at least for amd64, hppa, mips, sparc and x86 for now.

together with a bunch of other fixes backported from the 2.1.2 branch thanks to zmedico