Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 253137 - sys-apps/portage-2.1.6.4: warning about deprecation of "output" in etc-update
Summary: sys-apps/portage-2.1.6.4: warning about deprecation of "output" in etc-update
Status: RESOLVED WORKSFORME
Alias: None
Product: Portage Development
Classification: Unclassified
Component: Tools (show other bugs)
Hardware: AMD64 Linux
: High normal
Assignee: Portage team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-12-30 13:32 UTC by Melendro
Modified: 2009-01-09 20:50 UTC (History)
0 users

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

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Melendro 2008-12-30 13:32:12 UTC 
etc-update gives the following warning:

/usr/lib64/portage/pym/output.py:39: DeprecationWarning: DEPRECATION NOTICE: The output module was replaced by portage.output


Reproducible: Always

Steps to Reproduce:
Comment 1 Jeremy Olexa (darkside) (RETIRED) archtester gentoo-dev Security 2008-12-30 14:41:28 UTC 
Assigning to proper maintainer.

%% qfile etc-update
sys-apps/portage (/usr/sbin/etc-update)
Comment 2 Zac Medico gentoo-dev 2008-12-30 19:18:21 UTC 
It seems like you're not using the normal etc-update script that comes with portage-2.1.6.4. You can use `type etc-update` to find out what is being called.
Comment 3 Melendro 2008-12-31 15:01:30 UTC 
(In reply to comment #2)
> It seems like you're not using the normal etc-update script that comes with
> portage-2.1.6.4. You can use `type etc-update` to find out what is being
> called.
> 

asrock ~ # type etc-update
etc-update is /usr/sbin/etc-update

asrock ~ # ls -la /usr/sbin/etc-update
lrwxrwxrwx 1 root root 31 2008-12-29 12:59 /usr/sbin/etc-update -> ../lib64/portage/bin/etc-update

asrock ~ # ls -la /usr/lib64/portage/bin/etc-update
-rwxr-xr-x 1 root root 16170 2008-12-29 12:59 /usr/lib64/portage/bin/etc-update
Comment 4 Zac Medico gentoo-dev 2008-12-31 20:46:24 UTC 
It seems like it's using the correct etc-update version, so etc-update must be using the wrong portageq version. Please use `type portageq` to find out which portageq is being called.
Comment 5 Melendro 2009-01-01 14:16:14 UTC 
(In reply to comment #4)
> It seems like it's using the correct etc-update version, so etc-update must be
> using the wrong portageq version. Please use `type portageq` to find out which
> portageq is being called.
> 

asrock ~ # type portageq
portageq is /usr/bin/portageq
asrock ~ # ls -la /usr/bin/portageq
lrwxrwxrwx 1 root root 29 2008-12-29 12:59 /usr/bin/portageq -> ../lib64/portage/bin/portageq
asrock ~ # ls -la /usr/lib64/portage/bin/portageq
-rwxr-xr-x 1 root root 15414 2008-12-29 12:59 /usr/lib64/portage/bin/portageq
Comment 6 Zac Medico gentoo-dev 2009-01-08 22:56:22 UTC 
Can you produce the deprecation warning with the --debug option enabled and post the output?
Comment 7 Melendro 2009-01-09 15:06:49 UTC 
(In reply to comment #6)
> Can you produce the deprecation warning with the --debug option enabled and
> post the output?
> 

Somehow, the warning doesn't show anymore. I don't know what I did for this to happen.
You can close the bug.
Sorry for the inconveniences.
Comment 8 Zac Medico gentoo-dev 2009-01-09 20:50:27 UTC 
Ok, no problem. :)