[solved] Python 2.7.3 clashing with 3.2.3

[115552]

Hi all,

Few days ago while going through some major dependency hell with revdep-rebuild.

I ran `eselect python set 2` and switched to python3.2 instead of v2, still same problems..

I unmerged python 2.7.3 thinking I don't need it since I have 3.2.3 installed.

Then I noticed more dependancy issues and several apps not running as expected (bind, eclean, and some 20 other) as they require 2.7.3.

Now.. I can't get 2.7.3-r3 re-installed anymore! It compiles right but keeps complaining in the Install stage

Code: Select all

>>> Source compiled.
>>> Test phase [not enabled]: dev-lang/python-2.7.3-r3

>>> Install python-2.7.3-r3 into /var/tmp/portage/dev-lang/python-2.7.3-r3/image/ category dev-lang
make DESTDIR=/var/tmp/portage/dev-lang/python-2.7.3-r3/image/ altinstall maninstall 
>>> Completed installing python-2.7.3-r3 into /var/tmp/portage/dev-lang/python-2.7.3-r3/image/

>>> Installing (1 of 12) dev-lang/python-2.7.3-r3
 * checking 3953 files for package collisions
1000 files checked ...
2000 files checked ...
3000 files checked ...
 * This package will overwrite one or more files that may belong to other
 * packages (see list below). You can use a command such as `portageq
 * owners / <filename>` to identify the installed package that owns a
 * file. If portageq reports that only one package owns a file then do
 * NOT file a bug report. A bug report is only useful if it identifies at
 * least two or more packages that are known to install the same file(s).
 * If a collision occurs and you can not explain where the file came from
 * then you should simply ignore the collision since there is not enough
 * information to determine if a real problem exists. Please do NOT file
 * a bug report at http://bugs.gentoo.org unless you report exactly which
 * two packages install the same file(s). Once again, please do NOT file
 * a bug report unless you have completely understood the above message.
 * 
 * Detected file collision(s):
 * 
 *      /usr/share/gdb/auto-load/usr/lib64/-gdb.py
 * 
 * Searching all installed packages for file collisions...
 * 
 * Press Ctrl-C to Stop
 * 
 * dev-lang/python-3.2.3-r2:3.2::gentoo
 *      /usr/share/gdb/auto-load/usr/lib64/-gdb.py
 * 
 * Package 'dev-lang/python-2.7.3-r3' NOT merged due to file collisions.
 * If necessary, refer to your elog messages for the whole content of the
 * above message.

>>> Failed to install dev-lang/python-2.7.3-r3, Log file:

>>>  '/var/log/portage/dev-lang:python-2.7.3-r3:20130424-002724.log'

 * Messages for package dev-lang/python-2.7.3-r3:

 * This package will overwrite one or more files that may belong to other
 * packages (see list below). You can use a command such as `portageq
 * owners / <filename>` to identify the installed package that owns a
 * file. If portageq reports that only one package owns a file then do
 * NOT file a bug report. A bug report is only useful if it identifies at
 * least two or more packages that are known to install the same file(s).
 * If a collision occurs and you can not explain where the file came from
 * then you should simply ignore the collision since there is not enough
 * information to determine if a real problem exists. Please do NOT file
 * a bug report at http://bugs.gentoo.org unless you report exactly which
 * two packages install the same file(s). Once again, please do NOT file
 * a bug report unless you have completely understood the above message.
 * 
 * Detected file collision(s):
 * 
 *      /usr/share/gdb/auto-load/usr/lib64/-gdb.py
 * 
 * Searching all installed packages for file collisions...
 * 
 * Press Ctrl-C to Stop
 * 
 * dev-lang/python-3.2.3-r2:3.2::gentoo
 *      /usr/share/gdb/auto-load/usr/lib64/-gdb.py
 * 
 * Package 'dev-lang/python-2.7.3-r3' NOT merged due to file collisions.
 * If necessary, refer to your elog messages for the whole content of the
 * above message.

 * GNU info directory index is up-to-date.

I can't get many other apps installed as they complain that python v2 isn't installed, and to `eselect` another one. I did and can confirm i have 3.2 interpreter selected but they still don't comply..

Code: Select all

# eselect python list
Available Python interpreters:
  [1]   python3.2 *

I'm really stuck.. v3.2.3 is colliding with 2.7.3 for that gdb.py file (possibly other too?). I tried many ways to get around this but can't figure it out.

I thought of unmerging python 3.2.3 then emerging 2.7.3 but far too many depend on python, including portage.. Too risky ?

Code: Select all

# emerge --info
Portage 2.1.11.55 (default/linux/amd64/13.0, gcc-4.6.3, glibc-2.15-r3, 3.2.12-gentoo x86_64)
=================================================================
System uname: Linux-3.2.12-gentoo-x86_64-AMD_Sempron-tm-_Processor_LE-1200-with-gentoo-2.1
KiB Mem:     2058132 total,    454200 free
KiB Swap:    2016152 total,   2003544 free
Timestamp of tree: Wed, 24 Apr 2013 00:00:01 +0000
ld GNU ld (GNU Binutils) 2.22
ccache version 3.1.9 [disabled]
app-shells/bash:          4.2_p37
dev-lang/python:          3.2.3-r2
dev-util/ccache:          3.1.9
dev-util/cmake:           2.8.9
dev-util/pkgconfig:       0.28
sys-apps/baselayout:      2.1-r1
sys-apps/openrc:          0.11.8
sys-apps/sandbox:         2.5
sys-devel/autoconf:       2.13, 2.69
sys-devel/automake:       1.9.6-r3, 1.10.3, 1.11.6, 1.12.6
sys-devel/binutils:       2.22-r1
sys-devel/gcc:            4.6.3
sys-devel/gcc-config:     1.7.3
sys-devel/libtool:        2.4-r1
sys-devel/make:           3.82-r4
sys-kernel/linux-headers: 3.7 (virtual/os-headers)
sys-libs/glibc:           2.15-r3
Repositories: gentoo
ACCEPT_KEYWORDS="amd64"
ACCEPT_LICENSE="*"
CBUILD="x86_64-pc-linux-gnu"
CFLAGS="-O2 -pipe"
CHOST="x86_64-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/share/gnupg/qualified.txt /var/bind"
CONFIG_PROTECT_MASK="/etc/ca-certificates.conf /etc/env.d /etc/fonts/fonts.conf /etc/gconf /etc/gentoo-release /etc/php/apache2-php5.3/ext-active/ /etc/php/apache2-php5.4/ext-active/ /etc/php/cgi-php5.3/ext-active/ /etc/php/cgi-php5.4/ext-active/ /etc/php/cli-php5.3/ext-active/ /etc/php/cli-php5.4/ext-active/ /etc/revdep-rebuild /etc/sandbox.d /etc/terminfo"
CXXFLAGS="-O2 -pipe"
DISTDIR="/usr/portage/distfiles"
FCFLAGS="-O2 -pipe"
FEATURES="assume-digests binpkg-logs config-protect-if-modified distlocks ebuild-locks fixlafiles merge-sync news parallel-fetch protect-owned sandbox sfperms strict unknown-features-warn unmerge-logs unmerge-orphans userfetch xattr"
FFLAGS="-O2 -pipe"
GENTOO_MIRRORS="http://distfiles.gentoo.org"
LDFLAGS="-Wl,-O1 -Wl,--as-needed"
PKGDIR="/usr/portage/packages"
PORTAGE_CONFIGROOT="/"
PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --stats --human-readable --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY=""
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
USE="a52 aac aalib accessibility acl afs amd64 amr apache2 berkdb bzip2 cgi cli color cracklib crypt ctype cxx daemon dbus device-mapper diskio dri elf extensions fam fastcgi ffmpeg flac fontconfig fortran gd gdbm glib gnutls gpm hddtemp iconv imap innodb ipfilter ipod ipv6 jpeg lame lm_sensors mmx mmxext modules mp4 mp4live mudflap multilib mysql mysqli ncurses nfs nls nptl ogg openmp oss pam pcre php png policykit python qt3support readline remote rrdtool samba sensord session sockets sse sse2 ssl ssse3 tcpd theora threads unicode upnp v4l vcd vhosts vmware-tools vorbis web webdav webinterface x264 xattr xvid zlib" ABI_X86="64" ALSA_CARDS="ali5451 als4000 atiixp atiixp-modem bt87x ca0106 cmipci emu10k1x ens1370 ens1371 es1938 es1968 fm801 hda-intel intel8x0 intel8x0m maestro3 trident usb-audio via82xx via82xx-modem ymfpci" ALSA_PCM_PLUGINS="adpcm alaw asym copy dmix dshare dsnoop empty extplug file hooks iec958 ioplug ladspa lfloat linear meter mmap_emul mulaw multi null plug rate route share shm softvol" APACHE2_MODULES="authn_core authz_core socache_shmcb unixd actions alias auth_basic authn_alias authn_anon authn_dbm authn_default authn_file authz_dbm authz_default authz_groupfile authz_host authz_owner authz_user autoindex cache cgi cgid dav dav_fs dav_lock deflate dir disk_cache env expires ext_filter file_cache filter headers include info log_config logio mem_cache mime mime_magic negotiation rewrite setenvif speling status unique_id userdir usertrack vhost_alias" CALLIGRA_FEATURES="kexi words flow plan sheets stage tables krita karbon braindump" CAMERAS="ptp2" COLLECTD_PLUGINS="df interface irq load memory rrdtool swap syslog" ELIBC="glibc" GPSD_PROTOCOLS="ashtech aivdm earthmate evermore fv18 garmin garmintxt gpsclock itrax mtk3301 nmea ntrip navcom oceanserver oldstyle oncore rtcm104v2 rtcm104v3 sirf superstar2 timing tsip tripmate tnt ubx" INPUT_DEVICES="evdev keyboard mouse" KERNEL="linux" LCD_DEVICES="bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses text" LIBREOFFICE_EXTENSIONS="presenter-console presenter-minimizer" OFFICE_IMPLEMENTATION="libreoffice" PHP_TARGETS="php5-3" PYTHON_SINGLE_TARGET="python2_7" PYTHON_TARGETS="python2_7 python3_2" RUBY_TARGETS="ruby18 ruby19" USERLAND="GNU" VIDEO_CARDS="nvidia" XTABLES_ADDONS="quota2 psd pknock lscan length2 ipv4options ipset ipp2p iface geoip fuzzy condition tee tarpit sysrq steal rawnat logmark ipmark dhcpmac delude chaos account"
Unset:  CPPFLAGS, CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LANG, LC_ALL, MAKEOPTS, PORTAGE_BUNZIP2_COMMAND, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS, USE_PYTHON

What do you recommend I should do to resolve this ?

Edit: If there's a way to move everything to the later python v3, that's also on my list of solutions.

Thanks a lot.

[NeddySeagoon]

xushi,

Have you run python-updater ?

[ferreirafm]

Hi xushi,
Try to temporarily unmerge gdb and emerge python-2.7.3-r3 afterwards. This is a library provided to developers needing to create and manipulate hashed databases. It is a glib dependency for testing. After emerge python-2.7.3-r3, use eselect to set it, run the python-updater (--pretend first) and emerge gdb again.
As long as I now, those two python versions will coexist for a long time. So, it would be better to stay with 2.7 and eventually use 3.2 inside your scripts.
The gentoo experts may clarify, but I think that most of the programs were not ported to run pure python-3.2 in a very stable way. But such information might be outdated.
Hope it helps.
Best

EDIT: neddy, can we have your comments?

[NeddySeagoon]

ferreirafm,

Updated Gentoo systems should use Python-3.2 as the system wide Python.

Edit - don't you run python-updater after the new version of python has been selected?
or is your intention to do a system wide Python downgrade, remove gdb, then upgrade to Python-3.2 again ?

[ferreirafm]

Python-3.2 as the system wide Python.

I have been using 2.7 in a completely upgrade system without any problem. It could be harmful?

[NeddySeagoon]

ferreirafm,

Both should work. The stage3 tarballs have shipped with only Python-3.x for some time now, so thats what new users get as standard.

[ferreirafm]

neddy,
I think I'll go with 2.7 for a while. Matplotlib and pandas are not so stable as expected. And also I have a bunch of python scripts written in python-2.7. Anyway, thanks for the updated information.
Best

[115552]

Sorry, forgot to mention..

I didn't know about python-updater back then, but after reading about I ran it yesterday, and it put me back to square 1.. It gives me a big list of apps that need to be re-emerged, but they all fail with the same error below (of course, I can't eselect v2.7 as it doesn't exist...)

Code: Select all

'configure' finished successfully (1.556s)
  ./options()
  ./configure()
Configuration:
PREFIX                                   : /usr
LIBDIR                                   : /usr/lib64
 * python2_7: running run_in_build_dir waf-utils_src_configure --nopyc --nopyo
CCFLAGS="-O2 -pipe" LINKFLAGS="-Wl,-O1 -Wl,--as-needed" "./waf" --prefix=/usr --libdir=/usr/lib64 --nopyc --nopyo configure
 * ERROR: dev-python/pycairo-1.10.0-r4 failed (configure phase):
 *   configure failed
 * 
 * Call stack:
 *     ebuild.sh, line   93:  Called src_configure
 *   environment, line 3274:  Called python_foreach_impl 'run_in_build_dir' 'waf-utils_src_configure' '--nopyc' '--nopyo'
 *   environment, line 2986:  Called multibuild_foreach_variant '_python_multibuild_wrapper' 'run_in_build_dir' 'waf-utils_src_configure' '--nopyc' '--nopyo'
 *   environment, line 2360:  Called _multibuild_run '_python_multibuild_wrapper' 'run_in_build_dir' 'waf-utils_src_configure' '--nopyc' '--nopyo'
 *   environment, line 2358:  Called _python_multibuild_wrapper 'run_in_build_dir' 'waf-utils_src_configure' '--nopyc' '--nopyo'
 *   environment, line  534:  Called run_in_build_dir 'waf-utils_src_configure' '--nopyc' '--nopyo'
 *   environment, line 3258:  Called waf-utils_src_configure '--nopyc' '--nopyo'
 *   environment, line 3826:  Called die
 * The specific snippet of code:
 *           CCFLAGS="${CFLAGS}" LINKFLAGS="${LDFLAGS}" "${WAF_BINARY}" "--prefix=${EPREFIX}/usr" "${libdir}" "$@" configure || die "configure failed";
 * 
 * If you need support, post the output of `emerge --info '=dev-python/pycairo-1.10.0-r4'`,
 * the complete build log and the output of `emerge -pqv '=dev-python/pycairo-1.10.0-r4'`.
 * The complete build log is located at '/var/log/portage/dev-python:pycairo-1.10.0-r4:20130424-170002.log'.
 * For convenience, a symlink to the build log is located at '/var/tmp/portage/dev-python/pycairo-1.10.0-r4/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/dev-python/pycairo-1.10.0-r4/temp/environment'.
 * Working directory: '/var/tmp/portage/dev-python/pycairo-1.10.0-r4/work/pycairo-1.10.0-python2_7'
 * S: '/var/tmp/portage/dev-python/pycairo-1.10.0-r4/work/pycairo-1.10.0'

>>> Failed to emerge dev-python/pycairo-1.10.0-r4, Log file:

>>>  '/var/log/portage/dev-python:pycairo-1.10.0-r4:20130424-170002.log'

 * Messages for package dev-python/pycairo-1.10.0-r4:

 * Building package for python2.7 only while  is active.
 * Please consider switching the active Python 2 interpreter:
 * 
 *      eselect python set --python2 python2.7
 * 
 * Please note that after switching the active Python interpreter,
 * you may need to run 'python-updater' to rebuild affected packages.
 * 
 * For more information on python.eclass compatibility, please see
 * the appropriate python-r1 User's Guide chapter [1].
 * 
 * [1] http://www.gentoo.org/proj/en/Python/python-r1/user-guide.xml#doc_chap2
 * ERROR: dev-python/pycairo-1.10.0-r4 failed (configure phase):
 *   configure failed
 * 
 * Call stack:
 *     ebuild.sh, line   93:  Called src_configure
 *   environment, line 3275:  Called python_foreach_impl 'run_in_build_dir' 'waf-utils_src_configure' '--nopyc' '--nopyo'
 *   environment, line 2987:  Called multibuild_foreach_variant '_python_multibuild_wrapper' 'run_in_build_dir' 'waf-utils_src_configure' '--nopyc' '--nopyo'
 *   environment, line 2361:  Called _multibuild_run '_python_multibuild_wrapper' 'run_in_build_dir' 'waf-utils_src_configure' '--nopyc' '--nopyo'
 *   environment, line 2359:  Called _python_multibuild_wrapper 'run_in_build_dir' 'waf-utils_src_configure' '--nopyc' '--nopyo'
 *   environment, line  535:  Called run_in_build_dir 'waf-utils_src_configure' '--nopyc' '--nopyo'
 *   environment, line 3259:  Called waf-utils_src_configure '--nopyc' '--nopyo'
 *   environment, line 3827:  Called die
 * The specific snippet of code:
 *           CCFLAGS="${CFLAGS}" LINKFLAGS="${LDFLAGS}" "${WAF_BINARY}" "--prefix=${EPREFIX}/usr" "${libdir}" "$@" configure || die "configure failed";
 * 
 * If you need support, post the output of `emerge --info '=dev-python/pycairo-1.10.0-r4'`,
 * the complete build log and the output of `emerge -pqv '=dev-python/pycairo-1.10.0-r4'`.
 * The complete build log is located at '/var/log/portage/dev-python:pycairo-1.10.0-r4:20130424-022947.log'.
 * For convenience, a symlink to the build log is located at '/var/tmp/portage/dev-python/pycairo-1.10.0-r4/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/dev-python/pycairo-1.10.0-r4/temp/environment'.
 * Working directory: '/var/tmp/portage/dev-python/pycairo-1.10.0-r4/work/pycairo-1.10.0-python2_7'
 * S: '/var/tmp/portage/dev-python/pycairo-1.10.0-r4/work/pycairo-1.10.0'

 * Messages for package dev-python/pygtk-2.24.0-r3:

 * emerge --keep-going: dev-python/pygtk-2.24.0-r3 dropped because it requires
 * >=dev-python/pycairo-1.0.2[python_targets_python2_7(-),-python_single_targe
 * t_python2_6(-),-python_single_target_python2_7(-)], >=dev-python/pycairo-1.
 * 0.2[python_targets_python2_7(-),-python_single_target_python2_6(-),-python_
 * single_target_python2_7(-)]

 * Messages for package dev-lang/python-2.7.3-r3:

 * This package will overwrite one or more files that may belong to other
 * packages (see list below). You can use a command such as `portageq
 * owners / <filename>` to identify the installed package that owns a
 * file. If portageq reports that only one package owns a file then do
 * NOT file a bug report. A bug report is only useful if it identifies at
 * least two or more packages that are known to install the same file(s).
 * If a collision occurs and you can not explain where the file came from
 * then you should simply ignore the collision since there is not enough
 * information to determine if a real problem exists. Please do NOT file
 * a bug report at http://bugs.gentoo.org unless you report exactly which
 * two packages install the same file(s). Once again, please do NOT file
 * a bug report unless you have completely understood the above message.
 * 
 * Detected file collision(s):
 * 
 *      /usr/share/gdb/auto-load/usr/lib64/-gdb.py
 * 
 * Searching all installed packages for file collisions...
 * 
 * Press Ctrl-C to Stop
 * 
 * dev-lang/python-3.2.3-r2:3.2::gentoo
 *      /usr/share/gdb/auto-load/usr/lib64/-gdb.py
 * 
 * Package 'dev-lang/python-2.7.3-r3' NOT merged due to file collisions.
 * If necessary, refer to your elog messages for the whole content of the
 * above message.
 * One or more packages are either masked or have missing dependencies:
 * 
 *   =dev-lang/python-2* pulled in by:
 *     (sys-libs/cracklib-2.8.19::gentoo, installed)
 * 
 *   dev-lang/python:2.7[xml] pulled in by:
 *     (dev-libs/libxml2-2.9.0-r2::gentoo, installed)
 * 
 *   dev-lang/python:2.7 pulled in by:
 *     (dev-python/setuptools-0.6.30-r1::gentoo, installed)
 * 
 *   =dev-lang/python-2.7*[xml] pulled in by:
 *     (dev-libs/gobject-introspection-1.32.1::gentoo, installed)
 * 
 *   dev-lang/python:2.7 pulled in by:
 *     (virtual/python-argparse-1::gentoo, installed)
 * 
 * The resume list contains packages that are either masked or have
 * unsatisfied dependencies. Please restart/continue the operation
 * manually, or use --skipfirst to skip the first package in the list and
 * any other packages that may be masked or have missing dependencies.
 * 
 * The following 3 packages have failed to build or install:
 * 
 *  (dev-python/pycairo-1.10.0-r4::gentoo, ebuild scheduled for merge), Log file:
 *   '/var/log/portage/dev-python:pycairo-1.10.0-r4:20130424-022947.log'
 *  (dev-python/pygtk-2.24.0-r3::gentoo, ebuild scheduled for merge)
 *  (dev-lang/python-2.7.3-r3::gentoo, ebuild scheduled for merge), Log file:
 *   '/var/log/portage/dev-lang:python-2.7.3-r3:20130424-023025.log'

I'm going to try ferreirafm's suggestion of unmerging gdb, emerge python 2.7.3, then re-emerge gdb.

Once this is sorted, then I'll ask for help in figuring out why it's insisting on staying with v2.7 and doesn't like having v3.2 there..

I'll keep you updated asap. Thanks a lot!

[115552]

Alright after a lot more reading and testing, I think i'm half way there..

removed gdb
re-emerged python 2.7.3

again same error as above.

I even tried adding the following to make.conf, didn't do the trick.

PYTHON_TARGETS="python3_2"
PYTHON_SINGLE_TARGET="python3_2"


Did a lot of different scenarios with same result.. It still leads back to all these apps insisting on python 2.7, and python 2.7 not able to emerge due to that file collision (even though i unmerged gdb..)

So I moved /usr/share/gdb/auto-load/usr/lib64/-gdb.py to /var/tmp/

# eselect python update --python3 (i've done this many times before.. getting desperate and trying again)

And let it attepmpt to install python 2.7 again (i did an emerge on vim as it was broken)

# vim
vim: error while loading shared libraries: libpython2.6.so.1.0: cannot open shared object file: No such file or directory

# emerge -avt vim

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

Calculating dependencies... done!
[ebuild R ] app-editors/vim-7.3.409 USE="acl gpm nls python -X -cscope -debug -minimal -perl -ruby -vim-pager" 0 kB
[ebuild NS ] dev-lang/python-2.7.3-r3:2.7 [3.2.3-r2:3.2] USE="gdbm ipv6 ncurses readline sqlite ssl threads (wide-unicode) xml -berkdb -build -doc -examples -hardened -tk -wininst" 0 kB

This time finally python 2.7 installed successfully!!!

I'm now running python-updater and it's going through the list; So far so good (4 out of 30 successful)


However.. the main question now...

Why are vim and the other broken apps insisting on using python 2.7 ? What can I do to get them to recognise python 3.2 and just stick with that version so that I may uninstall 2.7 ?

[cwr]

Python 3.x isn't backward-compatible with Python 2.x. Apparently Gentoo has updated
portage to 3.x, so you _must_ have 3.x installed; however, there's a _lot_ of 2.x code out
there, and apparently some of it is in Vim.

Will

[ferreirafm]

Why are vim and the other broken apps insisting on using python 2.7 ? What can I do to get them to recognize python 3.2 and just stick with that version so that I may uninstall 2.7 ?

Have already you revdep-build your system?
If you got py2.7 installed, I think now you can migrate to py3.2 in the right way. Perhaps those things happened because you mess some stuff. Remember python is installed as a slot, so you can have both version coexisting at the same system and time. In my opinion, you should not remove py2.7.
Anyway to migrate to py3.7 do following:

Code: Select all

eselect python set python3.2 
python-updater 
emerge --depclean 
revdep-rebuild

G'Luck

[115552]

Thanks for the help so far.

To be honest I wasn't aware of python-updater until recently.

I can't run revdep-rebuild as there are too many collisions, and other errors in there that I need to sort out first (segfaults, dependancy hell, buggy apps that just fail to compile like netatalk). I do often get the resulting `emerge --oneshot` line and emerge the apps seperately, and I drilled down to a much smaller list. Some of the apps there thatn need emerging are the same as the ones I have errors with in this thread related to Python.

If I can solve the ones below, I can proceed with revdep-rebuild (and sorting out this new udev 200).

Python updator brought down the list of apps that need updating from ~30 down to 12 (see below)

Code: Select all

# python-updater 
 * Starting Python Updater...
 * Main active version of Python:    3.2
 * Active version of Python 2:       2.7
 * Active version of Python 3:       3.2
 * Globally supported Python ABIs in installed repositories:
 *   gentoo:                         2.4 2.5 2.6 2.7 3.1 3.2 3.3 2.5-jython 2.7-jython 2.7-pypy-1.7 2.7-pypy-1.8 2.7-pypy-1.9 2.7-pypy-2.0
 *   Adding to list: dev-libs/libxml2:2
 *   Adding to list: dev-libs/libxslt:0
 *   Adding to list: dev-python/argparse:0
 *   Adding to list: dev-python/gconf-python:2
 *   Adding to list: dev-python/libgnomecanvas-python:2
 *   Adding to list: dev-python/pygtk:2
 *   Adding to list: dev-python/pygtksourceview:2
 *   Adding to list: media-libs/alsa-lib:0
 *   Adding to list: net-analyzer/net-snmp:0
 *   Adding to list: sys-libs/cracklib:0
 * emerge -Dv1 --keep-going dev-libs/libxml2:2 dev-libs/libxslt:0 dev-python/argparse:0 dev-python/gconf-python:2 dev-python/libgnomecanvas-python:2 dev-python/pygtk:2 dev-python/pygtksourceview:2 media-libs/alsa-lib:0 net-analyzer/net-snmp:0 sys-libs/cracklib:0

These are the packages that would be merged, in order


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

Calculating dependencies... done!
[ebuild   R    ] sys-libs/cracklib-2.8.19  USE="nls python zlib -build -static-libs" 0 kB
[ebuild     U  ] dev-python/argparse-1.2.1-r2 [1.2.1] PYTHON_TARGETS="-python2_5% -python2_6% -python3_1%" 0 kB
[ebuild   R    ] dev-libs/libxml2-2.9.0-r2:2  USE="ipv6 python readline -debug -examples -icu -lzma -static-libs {-test}" PYTHON_TARGETS="-python2_5 -python2_6 -python2_7*" 0 kB
[ebuild  NS    ] dev-python/pygobject-2.28.6-r53:2 [3.2.2-r1:3] USE="-examples -libffi {-test}" PYTHON_TARGETS="-python2_6 -python2_7" 0 kB
[ebuild   R    ] media-libs/alsa-lib-1.0.26-r1  USE="python -alisp -debug -doc" PYTHON_SINGLE_TARGET="-python2_6 -python2_7*" PYTHON_TARGETS="-python2_6 -python2_7*" 0 kB
[ebuild   R    ] dev-libs/libxslt-1.1.28-r1  USE="crypt python -debug -static-libs" PYTHON_TARGETS="-python2_5 -python2_6 -python2_7*" 0 kB
[ebuild   R    ] net-analyzer/net-snmp-5.7.2_rc1  USE="bzip2 elf ipv6 lm_sensors python ssl tcpd zlib -X -doc -mfd-rewrites -minimal -perl -rpm (-selinux) -ucd-compat" 0 kB
[ebuild     U  ] dev-python/pygtk-2.24.0-r3:2 [2.24.0-r2:2] USE="-doc -examples {-test}" PYTHON_TARGETS="-python2_6% -python2_7%" 0 kB
[ebuild  N     ] dev-python/gnome-python-base-2.28.1:2  0 kB
[ebuild   R    ] dev-python/pygtksourceview-2.10.1:2  USE="-debug -doc" 0 kB
[ebuild   R    ] dev-python/libgnomecanvas-python-2.28.1:2  USE="-examples" 0 kB
[ebuild   R    ] dev-python/gconf-python-2.28.1:2  USE="-examples" 0 kB

Total: 12 packages (2 upgrades, 1 new, 1 in new slot, 8 reinstalls), Size of downloads: 0 kB

These all fail with the following error below. They're all the same so I'll just post one.

Code: Select all

>> Emerging (1 of 11) dev-python/argparse-1.2.1-r2
 * argparse-1.2.1.tar.gz SHA256 SHA512 WHIRLPOOL size ;-) ...                                                                                                                                                                                           [ ok ]
>>> Unpacking source...
>>> Unpacking argparse-1.2.1.tar.gz to /var/tmp/portage/dev-python/argparse-1.2.1-r2/work
>>> Source unpacked in /var/tmp/portage/dev-python/argparse-1.2.1-r2/work
>>> Preparing source in /var/tmp/portage/dev-python/argparse-1.2.1-r2/work/argparse-1.2.1 ...
>>> Source prepared.
>>> Configuring source in /var/tmp/portage/dev-python/argparse-1.2.1-r2/work/argparse-1.2.1 ...
>>> Source configured.
>>> Compiling source in /var/tmp/portage/dev-python/argparse-1.2.1-r2/work/argparse-1.2.1 ...
 * No Python implementation selected for the build. Please add one
 * of the following values to your PYTHON_TARGETS (in make.conf):
 *
 * python2_5 python2_6 python3_1

 * ERROR: dev-python/argparse-1.2.1-r2 failed (compile phase):
 *   No supported Python implementation in PYTHON_TARGETS.
 *
 * Call stack:
 *     ebuild.sh, line   93:  Called src_compile
 *   environment, line 3284:  Called distutils-r1_src_compile
 *   environment, line  879:  Called _distutils-r1_run_foreach_impl 'distutils-r1_python_compile'
 *   environment, line  209:  Called python_parallel_foreach_impl 'distutils-r1_run_phase' 'distutils-r1_python_compile'
 *   environment, line 3156:  Called _python_obtain_impls
 *   environment, line  569:  Called _python_validate_useflags
 *   environment, line  664:  Called die
 * The specific snippet of code:
 *       die "No supported Python implementation in PYTHON_TARGETS."
 *
 * If you need support, post the output of `emerge --info '=dev-python/argparse-1.2.1-r2'`,
 * the complete build log and the output of `emerge -pqv '=dev-python/argparse-1.2.1-r2'`.
 * The complete build log is located at '/var/log/portage/dev-python:argparse-1.2.1-r2:20130425-194339.log'.
 * For convenience, a symlink to the build log is located at '/var/tmp/portage/dev-python/argparse-1.2.1-r2/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/dev-python/argparse-1.2.1-r2/temp/environment'.
 * Working directory: '/var/tmp/portage/dev-python/argparse-1.2.1-r2/work/argparse-1.2.1'
 * S: '/var/tmp/portage/dev-python/argparse-1.2.1-r2/work/argparse-1.2.1'

>>> Failed to emerge dev-python/argparse-1.2.1-r2, Log file:

>>>  '/var/log/portage/dev-python:argparse-1.2.1-r2:20130425-194339.log'

The main area to focus on is

Code: Select all

 * No Python implementation selected for the build. Please add one
 * of the following values to your PYTHON_TARGETS (in make.conf):
 *
 * python2_5 python2_6 python3_1

 * ERROR: dev-python/argparse-1.2.1-r2 failed (compile phase):
 *   No supported Python implementation in PYTHON_TARGETS.

I have the following in my make.conf

Code: Select all

PYTHON_TARGETS="python3_2"
PYTHON_SINGLE_TARGET="python3_2"

Do I *have* to remove those 2 lines? Do I *have* to replace it with python 2.7 ??

My aim right now is to get everything moved to python v3, but am I to understand the 12 apps above don't support v3?

Ta.
Sam.

[ferreirafm]

Sam,
In my installation, all those argparse USE are unset. So, remove those lines from your make.conf and
run emerge --keep-going -vep system.
Run emerge --dep-clean and revdep afterwards.
G'Luck

[115552]

Did you literally mean the USE flags?

I removed

PYTHON_TARGETS="python3_2"
PYTHON_SINGLE_TARGET="python3_2"

after a lot more experimentation, and finally python 2.7 compiled, as well as a few of its apps via python-updater. There were a few that just wouldn't budge as they required other versions than 2_7 or 3_2. I unmerged those along with a few that were blocking my revdep-rebuild, and they weren't asked to be recompiled, so finally I got through my revdep-rebuild!

I still have libxml2 and libxslt, a few dev-python/... (dunno what they are), alsa (don't use sound) that still fail through python-updater but it doesn't seem like they're affecting anything right now. I'll see if I can unmerge them and if it asks for them again.

The only thing left is udev 200, which I won't go through as I can't afford my network to fubar as i'm connecting remotely..

Thanks a lot for your help all!