Jump to content

Photo

post-kits update profile problems

- - - - - profile

10 replies to this topic

#1
digifuzzy

digifuzzy

    Advanced Member

  • Members
  • PipPipPip
  • 101 posts
  • LocationCanada

I am having troubles with epro and profiles post-update to kits.

Every time I execute epro I get back the python error message:

Traceback (most recent call last):
  File "/usr/bin/epro", line 86, in <module>
    run_ego_module(install_path, action, ego_config, args)
  File "/usr/share/ego/python/ego_helpers.py", line 28, in run_ego_module
    mod = get_ego_module(install_path, modname)
  File "/usr/share/ego/python/ego_helpers.py", line 23, in get_ego_module
    return loader.load_module()
  File "<frozen importlib._bootstrap_external>", line 396, in _check_name_wrapper
  File "<frozen importlib._bootstrap_external>", line 817, in load_module
  File "<frozen importlib._bootstrap_external>", line 676, in load_module
  File "<frozen importlib._bootstrap>", line 268, in _load_module_shim
  File "<frozen importlib._bootstrap>", line 693, in _load
  File "<frozen importlib._bootstrap>", line 673, in _load_unlocked
  File "<frozen importlib._bootstrap_external>", line 673, in exec_module
  File "<frozen importlib._bootstrap>", line 222, in _call_with_frames_removed
  File "/usr/share/ego/modules/profile.ego", line 8, in <module>
    import portage
ImportError: No module named 'portage'

I suspect I missed something along the way prior to kits.

Suggestions? Help?



#2
nrc

nrc

    Advanced Member

  • Members
  • PipPipPip
  • 60 posts
  • LocationColumbus, Ohio, USA

What version of ego do you have installed?



#3
digifuzzy

digifuzzy

    Advanced Member

  • Members
  • PipPipPip
  • 101 posts
  • LocationCanada

[IP-] [  ] app-admin/ego-2.0.7:0



#4
nrc

nrc

    Advanced Member

  • Members
  • PipPipPip
  • 60 posts
  • LocationColumbus, Ohio, USA

That's current.  I agree, it sounds like you may have skipped a step somewhere. 

Post the output of "emerge --info app-admin/ego"



#5
Oleg Vinichenko

Oleg Vinichenko

    Staff

  • Moderators
  • 415 posts

this is due to the portage and ego both are built for different python versions.

show output of eselect python list


www.funtoo.org

#6
digifuzzy

digifuzzy

    Advanced Member

  • Members
  • PipPipPip
  • 101 posts
  • LocationCanada

this is due to the portage and ego both are built for different python versions.

show output of eselect python list

I was starting to dig into that notion. Python emerging was giving me strange messages about python 3.5.3 being masked but package.mask is a zero byte sized file.

eselect python list
Available Python interpreters, in order of preference:
  [1]   python3.5
  [2]   python3.4 (fallback)
  [3]   python2.7 (fallback)

I am currently working through the "Broken python and portage" section of  http://www.funtoo.or...m_resurrection.

I can work with a temporary copy of python 3.6 but emerge of portage(ver 2.3.8) complains about:

 * Messages for package sys-apps/portage-2.3.8:

 * ERROR: sys-apps/portage-2.3.8::core-kit failed (prerm phase):
 *   distutils-r1.eclass could not be found by inherit()

and updating to python 3.6.1-r1 stops at:

if test "xno" != "xno"  ; then \
	case no in \
		upgrade) ensurepip="--altinstall --upgrade" ;; \
		install|*) ensurepip="--altinstall" ;; \
	esac; \
	LD_LIBRARY_PATH=/var/tmp/portage/dev-lang/python-3.6.1-r1/work/Python-3.6.1:/tmp/Python-3.6.0 ./python -E -m ensurepip \
		$ensurepip --root=/var/tmp/portage/dev-lang/python-3.6.1-r1/image// ; \
fi
 * PT_PAX marking -m /var/tmp/portage/dev-lang/python-3.6.1-r1/image/usr/bin/python3.6m with scanelf
 * XATTR_PAX marking -me /var/tmp/portage/dev-lang/python-3.6.1-r1/image/usr/bin/python3.6m with setfattr
Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "/var/tmp/portage/dev-lang/python-3.6.1-r1/work/Python-3.6.1/Lib/distutils/sysconfig.py", line 14, in <module>
    import re
  File "/var/tmp/portage/dev-lang/python-3.6.1-r1/work/Python-3.6.1/Lib/re.py", line 122, in <module>
    import enum
  File "/var/tmp/portage/dev-lang/python-3.6.1-r1/work/Python-3.6.1/Lib/enum.py", line 2, in <module>
    from types import MappingProxyType, DynamicClassAttribute
  File "/var/tmp/portage/dev-lang/python-3.6.1-r1/work/Python-3.6.1/Lib/types.py", line 171, in <module>
    import functools as _functools
  File "/var/tmp/portage/dev-lang/python-3.6.1-r1/work/Python-3.6.1/Lib/functools.py", line 23, in <module>
    from weakref import WeakKeyDictionary
  File "/var/tmp/portage/dev-lang/python-3.6.1-r1/work/Python-3.6.1/Lib/weakref.py", line 12, in <module>
    from _weakref import (
ImportError: cannot import name '_remove_dead_weakref'
 * ERROR: dev-lang/python-3.6.1-r1::gentoo failed (install phase):
 *   (no error message)
 * 
 * Call stack:
 *     ebuild.sh, line  115:  Called src_install
 *   environment, line 4100:  Called python_export 'python3.6' 'EPYTHON' 'PYTHON_SITEDIR' 'PYTHON_SCRIPTDIR'
 *   environment, line 3379:  Called die
 * The specific snippet of code:
 *                   PYTHON_SITEDIR=$("${PYTHON}" -c 'import distutils.sysconfig; print(distutils.sysconfig.get_python_lib())') || die;



#7
Oleg Vinichenko

Oleg Vinichenko

    Staff

  • Moderators
  • 415 posts

i'm not able to understand this failures based on giving outputs. something went broken on your system due to non default settings, like unmasked pythons, etc.


www.funtoo.org

#8
digifuzzy

digifuzzy

    Advanced Member

  • Members
  • PipPipPip
  • 101 posts
  • LocationCanada

i'm not able to understand this failures based on giving outputs. something went broken on your system due to non default settings, like unmasked pythons, etc.

Starting to feel like a re-install.

Thanks for the help.



#9
Oleg Vinichenko

Oleg Vinichenko

    Staff

  • Moderators
  • 415 posts

you can do reinstall but now, it's maybe a good idea is to try using unmasked versions. so, now i guess it's python-3.6 is now the default python?


www.funtoo.org

#10
digifuzzy

digifuzzy

    Advanced Member

  • Members
  • PipPipPip
  • 101 posts
  • LocationCanada

you can do reinstall but now, it's maybe a good idea is to try using unmasked versions. so, now i guess it's python-3.6 is now the default python?

I suspect I had not maintained profile settings as well as I should. My fault for not paying attention to instructions. Confusion with past usage may have been the contributing cause of current problems.

When I did a "eselect profile show" I got the error message about profile settings not being found. When python/portage are completed, I'll try the epro command again to setup profile properly.

 

I cleaned out everything under /var/db/pkg and am in the process of reinstalling software using the method shown in the link I gave above for "Broken python and portage". There were a couple of circular dependencies to deal with (xz-utils/elt-patches, autoconfig, etc) and an error with libffi existing(rm existing /usr/lib64/libffi* files). Re-install appears to be going along well and the use flags given as to be used appear to be "sane".

 

Fingers crossed...



#11
digifuzzy

digifuzzy

    Advanced Member

  • Members
  • PipPipPip
  • 101 posts
  • LocationCanada

If you ended up here...

Looks like previous configurations have confused the issue.

Re-install seems the only recourse.





Reply to this topic



  


0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users