Bug 203984 – app-portage/etc-proposals-1.4: Initializing DB fails

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description Robert Schedel 2008-01-01 18:41:48 UTC]

The emerge succeeds and prints out that one should call "etc-proposals --init-db".

However, initializing the DB fails:

# etc-proposals --init-db
init_state_db() takes no arguments (4 given)

Reproducible: Always

Steps to Reproduce:
1. emerge etc-proposals
2. etc-proposals --init-db

Actual Results:  
# etc-proposals --init-db
init_state_db() takes no arguments (4 given)

Expected Results:  
Call should build the initial DB.

In fact in v1.4 of etc-proposals the function init_state_db does not have any args. Issue can be fixed by appending "(option, opt_str, value, parser)" in /usr/sbin/etc-proposals, similar to the other callback function in this file. v1.3 of etc-proposals did not yet use the OptionParser.

Looks like an upstream bug.

However, wondering how this could slip through at all and get into unstable (maybe older python version used in ebuild test?). Tested python version was:

# python -V
Python 2.4.4

[Comment 1 Björn Michaelsen 2008-01-01 21:39:01 UTC]

This is an upstream bug. Sorry for that. Its fixed in svn, I will release etc-proposals 1.4.1 tonight, so it can get version bumped to that version ASAP.

Again sorry for the inconvenience. As for this slipping through: There is no unittest for the starter script, and initializing the DB is done only once on most installations.

[Comment 2 Björn Michaelsen 2008-01-01 22:44:06 UTC]

Created attachment 139830 [details]
etcproposals-1.4.1.ebuild

I fixed the issue in the 1.4.1 version. The ebuild for it is attached.

[Comment 3 Tobias Scherbaum (RETIRED) 2008-01-02 16:00:56 UTC]

1.4.1 in CVS. Thanks for the fast response :)

[Comment 4 Markus Ullmann (RETIRED) 2008-01-03 00:56:57 UTC]

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