Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 392463 - rox-extra/roxcd: Deprecation Warning about of python_mod_cleanup()
Summary: rox-extra/roxcd: Deprecation Warning about of python_mod_cleanup()
Status: RESOLVED DUPLICATE of bug 452160
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: All Linux
: Normal minor (vote)
Assignee: No maintainer - Look at https://wiki.gentoo.org/wiki/Project:Proxy_Maintainers if you want to take care of it
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-11-29 20:29 UTC by Aljosha Papsch
Modified: 2013-03-02 18:26 UTC (History)
0 users

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

Attachments
emerge --info (emerge--info,4.37 KB, text/plain)
2011-11-29 20:29 UTC, Aljosha Papsch 		Details
View All 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 Aljosha Papsch 2011-11-29 20:29:11 UTC 
Created attachment 294239 [details]
emerge --info

When unmerging rox-extra/roxcd, emerge will print the following message:

 * Messages for package rox-extra/roxcd-0.5.4-r2:

 * 
 * Deprecation Warning: Usage of python_mod_cleanup() in packages not supporting installation
 * for multiple Python ABIs in EAPI <=2 is deprecated and will be disallowed on 2011-08-01.
 * Use EAPI >=3 and call python_mod_cleanup() with paths having appropriate syntax.
 * The ebuild needs to be fixed. Please report a bug, if it has not been already reported.
 *
Comment 1 emalele 2012-09-08 19:04:16 UTC 
The issue arises when Python version is set to v3.

Emerging the application goes well but it cannot execute when launched due to the (I suppose) different syntax in Python 3.
Comment 2 Aljosha Papsch 2012-09-09 01:16:09 UTC 
I'd consider that a different issue. This one is about a deprecation warning in the rox-extra/roxcd ebuild.
Comment 3 Pacho Ramos gentoo-dev 2013-03-02 18:26:38 UTC 

*** This bug has been marked as a duplicate of bug 452160 ***