Sandro

Hey everyone,
Just wanted to let you know that as of last night, I am happily running GNOME 3.32 with no issues (I did need to fix librsvg to get SVG's to display properly, but after that, it's working great.) I successfully upgraded my dev workstation from 1.3 to 1.4. If you want to upgrade from 1.3, or install a fresh 1.4 using one of our 1.4 stages (now available for Intel only), things should work well. 
One thing to note, on both the beta 1.4 stages and a 1.3 upgrade, you will need to manually run "eselect python set --python3 python3.7" to set python3.7 to be the default python interpreter instead of 3.6. Our stages will be fixed to have this set already but this is not done yet. I will also include a copy of my post from another place on the forums about upgrading from 1.3:
So, upgrade is pretty easy this time around.I will have instructions soon. But you can basically use "standard" upgrade steps. I recommend emerge -1 glibc gcc first, then emerge -auDN @world should generally work. Report any bugs related to upgrade like failed builds because often this can be fixed by tweaking dependencies. Overall the upgrade is MUCH easier than 1.2 -> 1.3.
One trick is to remember to "eselect python set --python3 python3.7" after python-3.7 is emerged to make it default. Also, mesa right now is very picky about USE flags related to video card. For example, if you don't have a card that supports vulkan, you cannot have vulkan in USE. Same with xa and other things that were more "permissible" before.
As of yesterday, I am now happily running gnome 3.32 and it is working perfectly. I would still call things "in beta" but the remaining issues (there is a "reboot doesn't work" issue currently active, due to a missing /run/initctl -> /dev/initctl symlink) should be worked out with minor package updates.

Hi All,
Within 12 hours, I plan to move 1.3-release to BETA status.
Along with this comes the very important change on 64-bit platforms -- I am removing multilib and making "pure64" compatibility the default. This means that 1.3-release builds with the x86-64bit arch will be 64-bit only.
This is done for a variety of reasons, most important of which is that the world has had a 64-bit PC instruction set for approximately 15 years. It is time to drop 32-bit support. For those who still need 32-bit support, it will be available via a Funtoo 32-bit chroot setup.
The story behind multilib is rather complex and interesting, and might be the focus of a future blog post, but for now, you will just have to trust me -- multilib support in Gentoo is a pain in the butt. It takes a lot of effort to work with and slows us down. Our efforts are best spent in other places, and chroot should work for the vast majority of users who truly are running a critical 32-bit application (other options are 32-bit containers, etc.)
EDIT: Upgrade Instructions Here: https://www.funtoo.org/Upgrade_Instructions/1.3-release
Best,
Daniel

Hi all,
Please test ego-2.6.0, which is currently masked for testing.
As many of you have noticed, there have been significant changes to kit generation and currently, ego is less "flexible" about mixing and matching kits from different releases. This is a side-effect of massively improved merge scripts, which now leverage python's asyncio, use a thread pool for database operations, and have much better internal design. I have put a lot of work into this new codebase and the new design is much better foundation for future development.
Currently, it is possible to select a custom xorg-kit or gnome-kit, but all other branches are locked down to the release. For those who may be upset -- We have never "officially" supported anything but the standard collection of release kits anyway, with some tweaks of xorg-kit and gnome-kit, so users who push the limits of mixing and matching kits right now have been using Funtoo in a way that is beyond the scope of what we intended to deliver, likely without realizing it. So if you want to use an unusual combination of kits -- awesome -- we want to support this officially in time, but we are working on getting there the right way rather than committing to supporting all these unusual combinations all at once.
If you have gotten accustomed to this flexibility in the past, know that this lack of flexibility is only temporary as we continue to build out our next generation of innovative technologies for managing kits. Re-enabling support for any old combination of kits is going backwards, in my opinion, and instead we need to move forward to OFFICIALLY support more combinations of kits. For the time being, you may need to write a small script to get things exactly how you want in meta-repo. We encourage people to use combinations we officially support if possible -- 1.2 with some variation of gnome-kit or xorg-kit. Things will be easier that way for the time being.
Also, we now have the 1.3-release kit names and definitions finalized, so this will allow us to move forward with 1.3 release development.
Best,
Daniel

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

ok, good job then :-) have fun

Hi All, 
I've just massively reworked the net-misc/dropbox ebuild to provide a much better experience in Funtoo and you should see this showing up in the next few hours. I couldn't get the Gentoo dropbox working reliably. Here is a list of all the changes:
Updated to dropbox-39.4.49.ebuild No longer has an initscript It now sets up ~/.dropbox-dist for each user who sets up dropbox (rather than having a system dropbox install) You don't need to be in the "dropbox" group to use the dropbox nautilus (gnome file browser) extension gnome support is built-in (as long as "gnome" is set in USE, which it is if you are using the GNOME mix-in.) Reworked the python 'dropbox' script to provide a better user experience and be optimal for Funtoo: if you start "dropbox" for the first time from GNOME, it will start a GTK+ installer to set up dropbox for you. if you don't have a GUI, you can still install dropbox The above two features are existing features of dropbox that were somewhat borked in Gentoo. At the end of the setup process, you are given instructions on how to enable dropbox on startup. dropbox command-line tool is also included. Please note that if you have nautilus-dropbox installed, you will need to remove it.
This should result in a really nice experience for dropbox users.
Use as follows:
# emerge dropbox (make sure it's 39.4.49 -- this is the new version.) (as regular user:) $ dropbox start -i This will initialize the ~/.dropbox-dist directory for the user via a command-line or GTK+ interface. Once this is done, dropbox start should be added to your .bash_login and/or .xprofile and can be run immediately to start dropbox in your current session.
Since the ebuild is completely new, the possibility of bugs exist. Please report bugs at https://bugs.funtoo.org . Thanks.
-Daniel

Hi All,
By default, we are now building stage3's using Funtoo Linux 1.2 release as default. This means that new installs will have this in their /etc/ego.conf:
[global]
release = 1.2
If you are still using release 1.0, that's fine -- your system will continue to use 1.0. When you upgrade to ego 2.4.1 or later, you will be able to set the release as above in your ego.conf, re-run "ego sync", and you will be upgraded to the 1.2 release. The release= setting is simply a short-hand for setting the various 1.2-related kits individually in the [kits] section, so many of you are already running 1.2.
Best,
Daniel

Could i see your /etc/ego.conf ?
I'm on 1.2ß

> [ebuild   R   ] media-gfx/exiv2-0.26_p20171104-r1  USE="nls png xmp -doc -exampl es -webready" ABI_X86="32 (64) (-x32)"  
Anyway i think you're not with 1.2ß kits.
If You're with 1.1, i think that you can upgrade your system to 1.2ß ....
To make it possible, You can use the howto ^^
I reccomend >=gentoo-sources [experimental] 4.16.8 to have a patched kernel vs "Meltdown" & "Spectre" without graphical troubles if you'll use GNome3 desktop.

Hi All,
The Funtoo Linux 1.2 release is now available for use. Many of us are now running Funtoo Linux 1.2. Here's how to upgrade your system to Funtoo Linux 1.2. Note that soon, 1.2 will be the "default" version of Funtoo Linux. For now, you need to perform certain steps to switch over. We're doing this so that power users can switch over right away, and so we can make things a lot easier for less-experienced users to upgrade to Funtoo Linux 1.2. One of the features I have been working on behind-the-scenes is an "easy upgrade" functionality for ego, to perform big updates automatically. This functionality is not yet ready, but is being worked on. When this "easy upgrade" functionality is ready, 1.2 will be released via "easy upgrade" to systems who have not yet upgraded.
For now, power users can upgrade by performing the following steps. First, select the new kits in your /etc/ego.conf:
[kits] core-kit = 1.2-prime security-kit = 1.2-prime kde-kit = 5.12-prime media-kit = 1.2-prime java-kit = 1.2-prime ruby-kit = 1.2-prime haskell-kit = 1.2-prime lisp-scheme-kit = 1.2-prime lang-kit = 1.2-prime dev-kit = 1.2-prime desktop-kit = 1.2-prime Then, perform the following steps, as root:
# ego sync This will activate the new kits. Now, if you have a /etc/portage/repos.conf/funtoo symlink, remove it:
# rm /etc/portage/repos.conf/funtoo Next,
# emerge -u1 gcc This will upgrade gcc. Next,
# emerge -u1 glibc libnsl libtirpc rpcsvc-proto Glibc will now be upgraded. Next,
# emerge -auDN @system This will upgrade your core system set of packages. Next,
# emerge -auDN @world This will upgrade all other packages. Next,
# emerge @preserved-rebuild This will rebuild packages that are linked to old libraries. Now, final step:
# revdep-rebuild --library 'libstdc++.so.6' -- --exclude sys-devel/gcc This will rebuild all remaining packages that need to be linked against the new libstdc++.
At this point, you are now upgraded to Funtoo Linux 1.2! Please report any bugs to https://bugs.funtoo.org and let us know of any issues you experience, either as part of the upgrade, related to dependencies, or related to functionality on your upgraded system.
Best,
Daniel Robbins

I use make.conf; I started to write it in 2010 using Gentoo; then I use it also if  may be "redundant" about some use flags; and i've a lot of USE and ~ 2000 ebuilds installed. Cause i like to have as more as possible the status and configuration of my system under my eyes :)

good

Ego no longer changes "gentoo:" to "core-kit:" in profiles
The bug report is closed and the source code on git master is fixed.
I install the ego-9999 live version built using fixed git source code until epro-2.3.4 is released.
funtoo rj # echo "app-admin/ego **" >> /etc/portage/package.accept_keywords/ego funtoo rj # emerge -1a ego  
 

Hiya!
All stages that Funtoo/Linux offer now gpg-signed.
Please, follow this instructions on how to proceed.
http://www.funtoo.org/GPG_Signatures

Hey All,
If you have a Funtoo container and would like to upgrade to kits, please contact me. I can reload your container so you can start with a 'fresh' system that is set up to work with kits from the beginning. The actual re-image process takes about 5 minutes to complete. It does require that you back up your important data, and once reloaded, your container will need your favorite apps emerged again.
Regards,
Daniel

Oops, I forgot I need to tweak the ebuild to reflect the new python module layout -- for now, this ebuild doesn't work, but will soon :)

ego-2.3.0 has been released and will be appearing in the tree in the next few hours. It is currently keyword masked but is available for testing and evaluation. It should be considered beta software for end-users -- our developers will be testing it but you are free to do so as well. Several bugs have been fixed (meta-repo sync robustness, avoiding a failure when run in a root-only-readable current working directory), and in addition several unit tests have been added, the entire code base has been heavily refactored, including a completely rewritten internal API for ego profile management.
Best Regards,
Daniel

OK, ebuild has been updated so it can now be tested.

Hey all, welcome to the new forums! Our old forum software has been upgraded to the latest version and I'm going to be working hard to help make this a really great resource for everyone.
Our "Funtoo Universe" section is set up in a traditional forum style, and "Help Central" is now in a Q&A-style mode. Let me know how you like the Q&A style mode. Both sets of forums allow you to tag posts as being answered and we have the ability to flag the best answer.

I just fixed login-related issues. Funtoo users who had not used the forums before were unable to log in.
I've also fixed the password reset link to go to our official password reset page, as well as the create account link. So logins should be working well.
One note is that if you were are user of the old forums, and you changed your 'displayname' to show something other than your username, then your forums account username will be your displayname. You can alternatively try logging in with your email as your username instead.
Everyone else should be good to go using their funtoo username (and password, of course) to log in here.

Also, in addition, I'm no longer updating master on the following kits: core-kit, security-kit, xorg-kit, gnome-kit, kde-kit, media-kit, perl-kit, python-kit. I made this change to reduce the clock time required to update our kits.

Hi all,
A multitude of new kits are coming your way. I'll give you a list of what they are and share other kit-related updates with you.
The new kits you'll be seeing soon are: ruby-kit, haskell-kit, ml-lang-kit, lisp-scheme-kit, and xfce-kit. With the exception of xfce-kit, these kits are all essentially sub-kits of dev-kit (and now have their own kit, just to try to pare down dev-kit a bit.) xfce-kit is for the XFCE 4.12 desktop environment.
In addition, we have snapshotted/frozen the following kits: *java-kit*, ruby-kit, haskell-kit, ml-lang-kit, lisp-scheme-kit, *dev-kit*, xfce-kit and *desktop-kit*. Note that the kits in red are ones that previously following gentoo-current, and are now snapshotted as of today (Oct 22). The other kits listed are the new kits.
With this wave of new kits, I am pushing forward the kit paradigm. With additional snapshotting of previously 'current' kits, I am putting funtoo's developer focus on getting the new 1.1-prime core-kit, media-kit and friends truly ready for production. The goal is to shift major updates to that they come via kit upgrades rather than a trickle of new package updates.
What should you expect over the rest of the year? Expect further stabilization of our now-snapshotted kits. Also, when PHP 7.2.0 is released, expect a php-kit that will be snapshotted at 7.2-prime rather than following current as it does now. You should also expect to see a new generation of kits made available so you can select more recent packages. Also on the radar are automated features to help switch kits cleanly -- think of these as things like perl-cleaner and friends but that get automatically triggered when you switch kits to ensure a smooth transition. And yes, you will likely see a few more kits added to the mix, along with new ego features.
With these new kits, the kit paradigm has been further advanced and will continue to advance. Along the way, you may feel that Funtoo Linux updates are getting 'stuck' or not going as quickly as you like, due to kits being frozen. If this impacts you, please provide us with feedback so we are aware of what things you need updated and why -- and understand that the pause in version bumps is more of a temporary phenomenon rather than a permanent reality. The updates will come -- in the form of kit bumps! The adjustment of our dev process will happen, and soon will reap rewards by offering stability as well as the latest ebuilds for you to choose from.
Please feel free to share your questions and concerns on this thread.
Best Regards,
Daniel

I already have a bug open and waiting for me to add the functionality to specify a kit from the command-line rather than having to edit the config file, so that will be appearing in ego shortly :)

Hi All,
ego-2.2.0 has been released, and is an important update, and will be appearing in meta-repo soon.
New functionality has been added to help you view kit configuration. To view your current kit settings, type:
# ego kit status This will display your current kit settings, as well as their stability level. The stability level is set by Funtoo and lets you know if you are running something we consider 'stable' or not. We recommend that all our users use kits that have a 'prime' stability level. Note that this is different than the kit having 'prime' in its name! When I create a kit, I may call it 1.1-prime if the goal is to make it production-quality, but the moment it is created, it is still considered 'dev' (developers only) status. Type "man ego-kit" for more information on this.
It is now also possible to view a similar listing, but one that displays ALL available kits and their stability levels, by typing:
# ego kit list This new release of ego also includes a host of other improvements, such as improvements to the "ego doc" MediaWiki parser.
Enjoy, Daniel

this is pretty much happens often with portage unable to solve conflicts. Daniel is working on improving this, notice that during many years portage developers didn't actually tried to fix it. For this particular problem:
akonadi cannot work with maridab-10.2, and 10.2 is the version you have installed on your box. if you put maridab-10.2 into package.mask, it will solve.