Bug 395561 – app-portage/gentoolkit-0.3.0.4-r5: "equery c" on nonexistent atom triggers deprecation warning

• Product: Portage Development
• Status: RESOLVED INVALID

[Description Michael Mol 2011-12-21 16:19:43 UTC]

While attempting to run 'equery c' on x11-base/xorg-drivers, I typo'd the atom name as 'x11base/xorg-drivers'. Consequentially, equery emitted a warning to stderr, and no output to stdout.

Reproducible: Always

Steps to Reproduce:
1. equery gobble/degook

Actual Results:  
/usr/lib64/portage/pym/portage/package/ebuild/config.py:353: UserWarning: 'cache.metadata_overlay.database' is deprecated: /etc/portage/modules
  (user_auxdbmodule, modules_file))

Expected Results:  
Either no output, or a warning that the specified atom doesn't exist or is invalid.

I'll have to attach the output of emerge --info; bugzilla complains that it's too large for submission.

Interestingly, the same warning crops up in there, too.

[Comment 1 Michael Mol 2011-12-21 16:20:31 UTC]

Created attachment 296573 [details]
emerge --info

[Comment 2 Jeroen Roovers (RETIRED) 2011-12-21 17:02:45 UTC]

How about -r5, which is going stable right now?

Also, the deprecation warning is a separate issue from the one you seemingly also wanted to report, namely that `equery c' should emit a "no such package" warning.

[Comment 3 Paul Varner (RETIRED) 2011-12-21 17:56:49 UTC]

The issue will still exist in -r5 since the only change between -r4 and -r5 was in the setup.py script.

[Comment 4 Michael Mol 2011-12-21 19:15:39 UTC]

Sorry; it's the deprecation warning that I'm interested in. I don't really care if 'equery c' larts me or not for specifying a nonexistent package, I just noticed the Python backtrace. I didn't even pick up on the deprecation warning occuring with 'emerge --info' until I got to the final stages of the bug report.

FWIW, the output of "equery c gobble/degook" with 0.3.0.5-r5 is the same

[Comment 5 Michael Mol 2011-12-21 19:17:12 UTC]

I'm running python-updater, now, on a hunch that it's a systemic python issue. So far:

kaylee shortcircuit # python-updater
/usr/lib64/portage/pym/portage/package/ebuild/config.py:353: UserWarning: 'cache.metadata_overlay.database' is deprecated: /etc/portage/modules
  (user_auxdbmodule, modules_file))
/usr/lib64/portage/pym/portage/package/ebuild/config.py:353: UserWarning: 'cache.metadata_overlay.database' is deprecated: /etc/portage/modules
  (user_auxdbmodule, modules_file))
 * Starting Python Updater...
 * Main active version of Python:  2.7
 * Active version of Python 2:     2.7
 * Active version of Python 3:     3.1
/usr/lib64/portage/pym/portage/package/ebuild/config.py:353: UserWarning: 'cache.metadata_overlay.database' is deprecated: /etc/portage/modules
  (user_auxdbmodule, modules_file))
/usr/lib64/portage/pym/portage/package/ebuild/config.py:353: UserWarning: 'cache.metadata_overlay.database' is deprecated: /etc/portage/modules
  (user_auxdbmodule, modules_file))
/usr/lib64/portage/pym/portage/package/ebuild/config.py:353: UserWarning: 'cache.metadata_overlay.database' is deprecated: /etc/portage/modules
  (user_auxdbmodule, modules_file))
/usr/lib64/portage/pym/portage/package/ebuild/config.py:353: UserWarning: 'cache.metadata_overlay.database' is deprecated: /etc/portage/modules
  (user_auxdbmodule, modules_file))

... I'll see if it clears up afterward, and if that was my problem all along.

This looks like it's not a gentoolkit-specific issue.

[Comment 6 Michael Mol 2011-12-21 19:24:59 UTC]

python-updater didn't fix it.

[Comment 7 Michael Mol 2012-07-08 17:03:53 UTC]

Turns out, I needed to remove a file from /etc/portage/modules. Going to see if I can close this bug, since it's no longer relevant. IIRC, I missed an ewarn at the time, so there's not even any need to put in an enhancement request for an ewarn.