savasten

Hello all and happy 2022!
So, I've been around for about 60 days now, and I wanted to share some of what I've been doing and some thoughts from Daniel and the development team.
I've been slowly getting to know the Funtoo ecosystem more and more each day.  From exploring the Funtoo system from a predominantly Gentoo context to combing through JIRA to having voice chats on Discord with some of y'all.
During our time in Gentoo, Daniel and I interacted with users via:
IRC, bugzilla, and mailing lists (and btw, the website was generated xml that Daniel had written and designed).  Later on, the forums came along and blogs came along between when Daniel left and when I left.  Since that time, the world has changed a little bit.  IRC has been replaced by Discord and Telegram, bugzilla replaced by JIRA, and not a lot happening on the mailing lists, and Twitter is a new addition (and now the website is another avenue for direct interaction for the Funtoo community.
Last week I invited everyone in the #general Discord channel to ping me if you'd like to schedule a 1 hour chat with me.  We can talk about anything you like. And now I’m opening that invite up to all of you as well. If you can see this and want to chat, please let me know so that we can schedule some together.   Although..based on the conversations I've already been having, I reckon we'll talk mostly about Gentoo and Funtoo things 🙂.
Thank you for your patience with all the JIRA emails lately, that's because I was going through each open ticket one by one, to bring everything up to date, and jump start some that had languished. I took a second pass through the tickets to tag them.  Within a day, community members were using the new tags/labels. Thank y'all for noticing and adopting 🙂
The goal is for us to start creating a plan for Funtoo development. In the coming weeks and months, we’ll start to communicate about where we’ll be focusing our efforts.  Most importantly, we’ll be focusing extensively on improving the experience for those of you who want to learn how to write ebuilds and autogens and want to share your ebuilds and autogens with the rest of the community.
 
I’ll provide another update next month,  near the 90-day mark.  Meanwhile, I’d love to chat with y’all..
 
Please feel free to book a time on my calendar, or get in touch with me via DM on Discord, Telegram or the forums. Every Tuesday and Thursday at 930PM PDT (530AM UTC +1 day) please join us in the Voice channel in Discord, where @sirisis leading an educational series via screenshare. Come learn about making ebuilds, autogen'ing ebuilds, and more.
 
Looking forward to get to know ayou.
 
Cheers,
Seemant

 

Hey everyone,
1.4 is almost ready to be released. Thanks so much to everyone who has contributed pull requests for 1.4 and tested 1.4. There's still a bunch of work to do, but there always will be and I believe 1.4 will be our most well-tested release so far.
After 1.4 is released, we will start development on 2.0, to be released some time in the Fall (Sept/Oct timeframe). I've been thinking about the release schedule a lot and I think that aiming for a .0 release every Fall seems to be a good idea. This means the work is completed well before the winter holidays, and fall in the US is a good season of change and looking forward to new things.
What I have left to do for 1.4 is to update the ARM builds to 1.4 and then also to update our documentation, release notes, upgrade steps and related docs. I want to incorporate the new video cards mix-ins into the official installation steps and not leave it to just be a "First Steps" item after install. This way, people can use the install docs to get their desktop environment of choice up and running, too.
I hope to get all this completed in the next few days.
 

We are not doing rolling release for the following reasons:
Too much time is spent on fixing various breakages coming in from Gentoo, which takes time away from other things... other things are more important such as new technology like fchroot and the upcoming containerization solution... If users are interested in certain packages being updated, I am encouraging them to submit a pull request and maintain these ebuilds themselves, so I am going to focus on helping YOU maintain ebuilds rather than have a few people (this has generally been Oleg) maintaining them for everyone. This model doesn't scale -- we all need to do a little bit rather than a few people doing a lot. See the YouTube channel here: https://www.youtube.com/channel/UCKmOY6p3c9hxv3vJMAF8vVw for tutorials Short-term, this means development slows down. But in reality, it will speed up development greatly. For those hanging out on IRC, you know that Oleg who has helped to maintain Funtoo for years has moved on to a new chapter in his life, so he is no longer active on Funtoo. But even though I am not slaving away over here, thanks to incoming pull requests Funtoo is continuing to move forward and be responsive to user needs.
So think of it as a course correction as we become more agile and community-oriented, and be part of the solution. If you are reading this, it means you are part of the Funtoo community and just as able to contribute to Funtoo as anyone else (maybe with some tutorials/videos to help).
When I work on technologies, I am trying more to work on key tools that help the community be more productive (like fchroot) rather than focusing on specific ebuilds, which I am leaving to the community to manage using pull requests.
Best,
Daniel

I believe that Funtoo has switched to a more stable release cycle (Not exactly, more like a break less stuff cycle).  @drobbins has also released some great videos on his youtube channel for submitting put requests to have the community start helping with the updates. 

Sorry for the questions?  
sshd running by default - did you file a bug report?
Have you all checked out the youtube videos on contributing?
Lets fix these things.  We are Funtoo, @drobbins, @Oleg Vinichenko and other regulars are the directors.  If it is broken fix it. 

Funtoo is my favorite Linux distro. I've been using it enthusiastically since at least 2012. I've been tinkering a lot with FreeBSD for the past 3 years which has divided my attention, but I still use Funtoo as my primary desktop OS.
Here's my concern. I'm using Funtoo 1.2. In the past few months, I've encountered a LOT of blockers when trying to emerge world. Sometimes the blockers are things that don't exist in the portage tree, sometimes they are things which need to be unmasked, and sometimes they are things which need to be unmasked by keyword. I went through a short period of time where I filed a lot of bugs about these blockers. But one bug I filed was dismissed as a "workaround" because I filed a bug about something which needed to be unmasked.
My feeling on the matter is that, if I try to emerge a package that it unmasked by default, then it should emerge without any problem. It should NOT require me to unmask anything or unmask something by keyword. Only ebuilds which are themselves masked or keyworded should rely on other ebuilds which are masked or keyworded. That's my opinion, but if that is not the opinion of the Funtoo project, I ask that such opinions be made plain so that people like me who love the project and want to contribute do not become nuisances by filing bugs or complaining when that is not the goal of the project. But at the same time, if that is not the goal of the project, then why are such bug reports being closed as "workaround" instead of being properly fixed? I asked Daniel and the rest of the Funtoo devs to please make a clear statement about these sorts of things so that users like me who are trying to help can be a genuine help without being a nuisance.

the proto blocks should be resolved.

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