Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 138317 - sys-apps/portage-2.1.1_pre1-r3: "emerge --sync" TypeError calling chk_updated_cfg_files
Summary: sys-apps/portage-2.1.1_pre1-r3: "emerge --sync" TypeError calling chk_updated...
Status: RESOLVED DUPLICATE of bug 138195
Alias: None
Product: Portage Development
Classification: Unclassified
Component: Core (show other bugs)
Hardware: All Linux
: High normal (vote)
Assignee: Portage team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-06-28 00:54 UTC by Joe Wells
Modified: 2006-06-28 10:47 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments
Output of "emerge -info" on my system. (emerge-info-output,8.30 KB, text/plain)
2006-06-28 00:56 UTC, Joe Wells
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Joe Wells 2006-06-28 00:54:49 UTC
With sys-apps/portage-2.1.1_pre1-r3 installed, running the command

  emerge --verbose --sync

fails after syncing with these messages:

----------------------------------------------------------------------
>>> Updating Portage cache:  100%
Traceback (most recent call last):
  File "/usr/bin/emerge", line 3723, in ?
    emerge_main()
  File "/usr/bin/emerge", line 3693, in emerge_main
    action_sync(myopts, myaction)
  File "/usr/bin/emerge", line 2734, in action_sync
    chk_updated_cfg_files()
TypeError: chk_updated_cfg_files() takes exactly 2 arguments (0 given)
----------------------------------------------------------------------

Can you please help?

Output of "emerge --info" attached separately.
Comment 1 Joe Wells 2006-06-28 00:56:11 UTC
Created attachment 90340 [details]
Output of "emerge -info" on my system.
Comment 2 Zac Medico gentoo-dev 2006-06-28 01:00:22 UTC

*** This bug has been marked as a duplicate of 138195 ***
Comment 3 Joe Wells 2006-06-28 04:43:04 UTC
(In reply to comment #2)
> *** This bug has been marked as a duplicate of 138195 ***

Just for the record, as it seems this bug is now fixed:

After inspection, it is clear that the bug in this bug report is not a
duplicate of bug 138195.  Bug 138195 is about an uninitialized
variable, while this bug report is about a wrong number of arguments.
Searching further, I found that this bug report is the same problem as
reported in bug 138131 comment 1, but a different bug from the initial
report in bug 138131.
Comment 4 Zac Medico gentoo-dev 2006-06-28 10:47:49 UTC
Indeed, you are correct.  Both problems are closely related though.  The error reported in bug 138195 is the result of an incomplete patch for the error reported in this bug.  I've explained my mistake here:

http://bugs.gentoo.org/show_bug.cgi?id=138131#c8