pross

Hey all,
As part of getting Funtoo updated for next-release, I updated some packages which caused some temporary disruption for desktop users.
The culprit was the update to glib-2.70.0. This update, we found, required several packages, particularly those related to session management, like gnome-session, cinnamon-session, etc. to be rebuilt. Rev bumps were added for all necessary packages that needed rebuilding. If you find a package that needs a rebuild that didn't get automatically rebuilt -- PLEASE -- for the love of God -- open a bug! ?
If that wasn't enough, there was ALSO another problem. Basically, glib-2.70.0 has a bunch of 'hardening' functionality (this was actually added in 2.67.2 but we were on an earlier version up until recently). This hardening prevented gnome-keyring-daemon from connecting to dbus. Which in turn prevented anything from connecting to gnome-keyring. So things like google-chrome would hang when they tried to connect to gnome-keyring, since they never got a response. I have added a new gnome-keyring package that works around this issue by removing 'caps' from the gnome-keyring-daemon binary. gnome-keyring 3.60.0-r1 should now happily connect to dbus and this issue should be resolved.
As of right now -- after a world update on your system -- your desktop environment should be happy! If this is not the case and you have to rebuild something or you find some component not working. Please -- open a bug! We want to know about any issues you are encountering and a 100% reliable desktop is super-important for our users.
Best,
Daniel

New stages have been uploaded January 24,2021.
Changes added in the new stages for ease of installation include:
New perl, ruby, qt, and llvm kits.
Python3 Spidermonkey support.
Replaced GDM with SDDM as default default desktop manager.
New NVIDIA drivers support to work with newer hardware.
 
Flatpak is now the official way to install Steam now. It works great with Intel, AMD, and Nvidia gpus hardware is updated regularly, and is easy to install!
https://www.funtoo.org/Steam
https://www.funtoo.org/Flatpak
 
Lots of hard work has been done with autogenning packages. What does this mean for you? It means that your favorite packages will be automatically updated as new releases come out. No more waiting for updates.
Also, freshly autogenned ck-sources!
Also, behind the scenes, hard work is being done on a new Funtoo power management system!
Special thanks to the many people who contributed their time to help!
 
If you have questions, issues, or just want to drop in and say hello you can find us on Discord https://discord.gg/BNUSpUU or Telegram https://t.me/funtoolinux
 
Installation Instructions: https://www.funtoo.org/Install/Introduction
Find and download your Subarch here: https://www.funtoo.org/Subarches
Find a bug or want an improvement? https://bugs.funtoo.org (once you have created a user account, you will need to login with your username in all lowercase)
We hope you enjoy the new Stage updates and thank you for choosing to use Funtoo!

Hi All,
In order to have more predictability for users, Funtoo Linux is going to adopt a six-month release schedule starting in 2018. Our kits are currently at 1.0-prime, and we are going to skip over 1.1-prime (it didn't get done fast enough) and jump to 1.2-prime. We are going to start development on 1.2-prime today, December 28, 2017, with a planned release of the production 1.2-prime on January 21, 2018. We will then maintain the 1.2-prime kits for the next six months, until they are replaced with 1.3-prime.
The schedule in detail is as follows:
December, 28, 2017: start development on 1.2
January 1, 2018: we will be rolling out a python-modules-kit and perl-modules-kit as new kits (for 1.0+)
January 4, 2018: Alpha release of 1.2
January 11, 2018: Beta release of 1.2
We will have a release candidate when we feel we are ready, with a scheduled production release on January 21, 2018.
On February 1, 2018, the 1.0-prime kits will be deprecated and users will be migrated to the 1.2-prime kits (this should be seamless unless you've hard-coded 1.0 or 1.1-prime kits in ego.conf.)

For 1.2-prime, what we are going to attempt to deliver is a default gcc of 6.4 and all ebuilds updated to be in sync with Gentoo as of January 2018. We will be using a 'current' (non-snapshotted tree) until around January 4th when we will freeze the tree and then will start backporting security fixes and updates.
In a few hours, the 1.2-prime kits will appear but will be tagged as DEVELOPMENT quality, so they should not be used until they are made default. I will post updates here on our progress.
Regards,
Daniel