Bug 418245 – dev-python/dbus-python-1.1.0: restrict python 3.0? - Active version of CPython 3 is not supported by dev-python/dbus-python-1.1.0

• Product: Gentoo Linux
• Status: RESOLVED DUPLICATE

[Description Martin Mokrejš 2012-05-30 13:44:45 UTC]

# python-updater
 * Starting Python Updater...
 * Main active version of Python:    2.7
 * Active version of Python 2:       2.7
 * Active version of Python 3:       3.1
 * Globally supported Python ABIs in installed repositories:
 *   gentoo:                         2.4 2.5 2.6 2.7 3.1 3.2 2.5-jython 2.7-pypy-1.7 2.7-pypy-1.8
 *   gentoo-haskell:                 2.4 2.5 2.6 2.7 3.1 3.2 2.5-jython 2.7-pypy-1.7 2.7-pypy-1.8
 *   science:                        2.4 2.5 2.6 2.7 3.1 3.2 2.5-jython 2.7-pypy-1.7 2.7-pypy-1.8
 *   x-layman:                       2.4 2.5 2.6 2.7 3.1 3.2 2.5-jython 2.7-pypy-1.7 2.7-pypy-1.8
 *   x-portage:                      2.4 2.5 2.6 2.7 3.1 3.2 2.5-jython 2.7-pypy-1.7 2.7-pypy-1.8
 *   Adding to list: dev-python/dbus-python:0
 * emerge -Dv1 --keep-going dev-python/dbus-python:0

 * IMPORTANT: 1 news items need reading for repository 'gentoo'.
 * Use eselect news to read news items.


These are the packages that would be merged, in order:

Calculating dependencies... done!
[ebuild     U  ] dev-python/dbus-python-1.1.0 [1.0.0] USE="-doc -examples -test" 0 kB

Total: 1 package (1 upgrade), Size of downloads: 0 kB


>>> Verifying ebuild manifests

>>> Emerging (1 of 1) dev-python/dbus-python-1.1.0
 * dbus-python-1.1.0.tar.gz RMD160 SHA1 SHA256 size ;-) ...                                                                                                                                                                                                                                                             [ ok ]
 * ERROR: dev-python/dbus-python-1.1.0 failed (setup phase):
 *   Active version of CPython 3 is not supported by dev-python/dbus-python-1.1.0
 * 
 * Call stack:
 *       ebuild.sh, line  85:  Called pkg_setup
 *       ebuild.sh, line 319:  Called python_pkg_setup
 *   python.eclass, line 431:  Called _python_calculate_PYTHON_ABIS
 *   python.eclass, line 845:  Called die
 * The specific snippet of code:
 *                                              die "Active version of CPython 3 is not supported by ${CATEGORY}/${PF}"
 * 
 * If you need support, post the output of 'emerge --info =dev-python/dbus-python-1.1.0',
 * the complete build log and the output of 'emerge -pqv =dev-python/dbus-python-1.1.0'.
 * The complete build log is located at '/var/tmp/portage/dev-python/dbus-python-1.1.0/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/dev-python/dbus-python-1.1.0/temp/die.env'.
 * S: '/var/tmp/portage/dev-python/dbus-python-1.1.0/work/dbus-python-1.1.0'

>>> Failed to emerge dev-python/dbus-python-1.1.0, Log file:

[Comment 1 Samuli Suominen (RETIRED) 2012-05-30 13:53:57 UTC]

Time to migrate from Python 3.1 to Python 3.2 and uninstall Python 3.1.

Something like,

# emerge -1 python:3.2
# eselect python list
# eselect python set <pick the one for 3.2>
# python-updater
# emerge -C python:3.1

No real bug here, other than outdated system

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

[Comment 2 Martin Mokrejš 2012-05-30 14:14:31 UTC]

(In reply to comment #1)
> Time to migrate from Python 3.1 to Python 3.2 and uninstall Python 3.1.
> 
> Something like,
> 
> # emerge -1 python:3.2
> # eselect python list
> # eselect python set <pick the one for 3.2>
> # python-updater
> # emerge -C python:3.1
> 
> No real bug here, other than outdated system

... outdated ~amd64, yes. ;) Too many cross-blocks all over and I just have no time to fight that all.

But I am still at python-2.7 and want to stay! I have no time to convert to 3.x, sorry. Actually will have to tweak my tools to run even under 2.5. :(( I still think the dbus-python ebuild should not try to install itself on 3.1 or whatever if that is because of some incompatibility or if it is unsupported version.

[Comment 3 Samuli Suominen (RETIRED) 2012-05-30 14:23:35 UTC]

(In reply to comment #2)
> (In reply to comment #1)
> > Time to migrate from Python 3.1 to Python 3.2 and uninstall Python 3.1.
> > 
> > Something like,
> > 
> > # emerge -1 python:3.2
> > # eselect python list
> > # eselect python set <pick the one for 3.2>
> > # python-updater
> > # emerge -C python:3.1
> > 
> > No real bug here, other than outdated system
> 
> ... outdated ~amd64, yes. ;) Too many cross-blocks all over and I just have
> no time to fight that all.
> 
> But I am still at python-2.7 and want to stay!  I have no time to convert to
> 3.x, sorry. Actually will have to tweak my tools to run even under 2.5. :((

That's OK, you just have to uninstall 3.1 and install 3.2 but you can keep your active version at 2.7

> I still think the dbus-python ebuild should not try to install itself on 3.1
> or whatever if that is because of some incompatibility or if it is
> unsupported version.

I agree, it's stupid to not inform users about the uselessness of 3.1, I've tried to make the case in bug 416171 without luck. This bug is a direct result of it.

[Comment 4 Dirkjan Ochtman (RETIRED) 2012-05-30 14:34:23 UTC]

You neglect to mention it would be fairly trivial for the maintainers to make sure dbus-python doesn't get installed on 3.1.

[Comment 5 Samuli Suominen (RETIRED) 2012-05-30 15:00:53 UTC]

(In reply to comment #4)
> You neglect to mention it would be fairly trivial for the maintainers to
> make sure dbus-python doesn't get installed on 3.1.

You mean going through every possible dbus-python consumer, leading to PyQt4 consumers, and add the same RESTRICT_PYTHON="3.1" to them?
That seems like a lot of unnecessary work for maintainers I'm going to decline outright.

[Comment 6 Arfrever Frehtes Taifersar Arahesis 2012-05-30 18:04:57 UTC]

dbus-python-1.1.0 actually works with CPython 3.1.
Test suite would require changing 1 line in 1 file.
dev-python/dbus-python-1.1.0-r1000::progress preserves support for CPython 3.1.

[Comment 7 Samuli Suominen (RETIRED) 2012-06-30 07:53:13 UTC]

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