Jump to content
funtoo forums
  • 0
Sandro

It's ok or not ?

Question

I don't know if is it is normal or not :|

 

 

 rename metadata/md5-cache/sys-cluster/{kube-scheduler-1.7.3 => kube-scheduler-1.7.5} (83%) 
create mode 100644 metadata/md5-cache/sys-kernel/gentoo-sources-4.13.1
create mode 100644 metadata/md5-cache/sys-kernel/gentoo-sources-4.9.49
rename sys-cluster/kube-proxy/{kube-proxy-1.7.3-r1.ebuild => kube-proxy-1.7.5.ebuild} (100%)
rename sys-cluster/kube-scheduler/{kube-scheduler-1.7.3.ebuild => kube-scheduler-1.7.5.ebuild} (100%)
create mode 100644 sys-kernel/gentoo-sources/gentoo-sources-4.13.1.ebuild
create mode 100644 sys-kernel/gentoo-sources/gentoo-sources-4.9.49.ebuild
(cd /var/git/meta-repo/kits/nokit && git rev-parse HEAD)
Sync successful and kits in alignment! :) 
Updating profiles... 
Traceback (most recent call last):
 File "/usr/bin/ego", line 86, in <module>
   run_ego_module(install_path, action, ego_config, args)
 File "/usr/share/ego/python/ego_helpers.py", line 30, in run_ego_module
   mod.main(install_path, config, args)
 File "/usr/share/ego/modules/sync.ego", line 213, in main
   s.sync_meta_repo()
 File "/usr/share/ego/modules/sync.ego", line 150, in sync_meta_repo
   ego_profile = get_ego_module(self.install_path, "profile")
 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 use only "ego sync && emerge -DNu world --with-bdeps=y"

 

Thanx for answers :)

Share this post


Link to post
Share on other sites

2 answers to this question

Recommended Posts

  • 0

I've no idea what it is but ... a python traceback can't be "normal" ...

 

It looks like some kind of debris left over by migrating from portage to meta-repo/ego/kits/whatever the evil bofh is doing.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×