Leaderboard

The 1.0 release of Funtoo Linux is not going to be maintained after September 30, 2018. So please be sure to upgrade your systems to Funtoo Linux 1.2 using https://www.funtoo.org/Upgrade_Instructions so that you will continue to get updates! We will also be starting development on Funtoo Linux 1.3 in a few days, on August 31. We are moving to a new agile (scrum) process, where we will be doing 1-week sprints (time-constrained sets of work). Our work will include some portion of fixes for 1.2 and some new work on 1.3. When we as a team decide that 1.3 is ready for various milestones (alpha, beta, release candidate) we will mark it as such. Thus, we have no hard deadline for 1.3 as I do not want to try to hit arbitrary dates that are not based on the actual work. But we will get there, sooner rather than later!

ok, good job then :-) have fun

Hello Sandro, I got the same issue with ego and I solved the issue with: $ sudo vim /etc/portage/package.use # added with comment: solve problem for ego sync >=app-admin/ego-2.4.2 python_targets_python3_6 >=sys-apps/portage-2.3.47 python_targets_python3_6 Then I selected Python 3_6 as default for my system with $ sudo eselect python list #then $ sudo eselect python set 4 Then i reinstalled ego with: $ sudo emerge --ask ego After this I just ran: $ ego sync And everything works back like it should ^^, the main issue was that one day I updated my system with some python 3_4 flags and broke a part of the system, nothing to worried about or no need to re-install from scratch ^^ I see it is from 2017, but maybe it helps you and if not it may help another user. Cheers and have fun :-)

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 :)