NikosAlexandris

I tried to make this clear in the announcement, but it is worth explaining in more detail -- Sabayon Linux and Funtoo Linux are going to remain distinct things.
We will make the Funtoo tree work for Sabayon so we can all contribute to the same set of packages.
There is no implied change to either Funtoo or Sabayon, besides Sabayon moving to use the Funtoo tree, by announcing this collaboration. Each project continues to make decisions for its own community with no obligation to switch to different technologies unless one project decides it wants to.
Over time, we will be collaborating on technology and some technology will be shared -- because it will be designed to make both Sabayon and Funtoo communities happy. Due to the nature of ebuilds, we can build two separate projects using the same base as a start.
Sabayon has not had a lot of public activity because they have been heavily working on their next evolution of the OS. They have been very busy, but it has been behind the scenes.
Best,
Daniel

Since they're pulling gentoo packages I'm not sure how much difference the freshness of the ISO makes.  I assume it's a stage4/installer package and you can build from there. For comparison, Funtoo 1.4 was released Sept '19.
That's the interesting thing about this, if they have an easy installer and a more friendly package manager it could significantly extend Funtoo's reach.  They are at least in the top 100 on distrowatch.  That probably represents at least a doubling of users benefiting from Funtoo developments.
The one concern for me is that Sabayon currently ships with systemd as the default init - a definite no for me.

I have posted an announcement on www.funtoo.org that we are doing an official "End of Year" pause for 2020.
2020 has been an interesting year and this is a good time to take a break if you have vacation. Funtoo will be back in 2021. Tree updates will be minimal during the break.

i pulled the better-initramfs stuff out, the ebuilds missing from portage, & we should not depend on remote initramfs images.  debian-sources initramfs supports dmcrypt && luks && lvm....  it does all of them.  i can get my build to boot, but it's a dirty ugly hack to get it to boot.  its a misplaced detail SOMEWHERE....  and i think it's not supporting partlabel, requiring uuid for crypt root.  i point the misloaded initrd @ /dev/sdc3 and it unlocks & finishes booting fine.
it's all gravy now

Hey guys, having some problems trying to install pango mm:
pangomm
and libreoffice-bin:
!!! Multiple package instances within a single package slot have been pulled
!!! into the dependency graph, resulting in a slot conflict:
dev-libs/boost:0
  (dev-libs/boost-1.65.0:0/1.65.0::core-kit, ebuild scheduled for merge) pulled in by
    dev-libs/boost:0/1.65.0 required by (app-office/libreoffice-bin-6.2.4.2:0/0::desktop-kit, ebuild scheduled for merge)
                  ^^^^^^^^^                                                                                               
  (dev-libs/boost-1.70.0:0/1.70.0::core-kit, installed) pulled in by
    >=dev-libs/boost-1.65.1:0/1.70.0= required by (sys-fs/cryfs-0.10.2:0/0::core-kit, installed)
    ^^               ^^^^^^^^^^^^^^^^                                                            
    (and 1 more with the same problem)
app-text/hunspell:0
  (app-text/hunspell-1.6.2-r1:0/1.6::text-kit, ebuild scheduled for merge) pulled in by
    app-text/hunspell:0/1.6 required by (app-office/libreoffice-bin-6.2.4.2:0/0::desktop-kit, ebuild scheduled for merge)
                     ^^^^^^                                                                                               
  (app-text/hunspell-1.7.0:0/1.7::text-kit, installed) pulled in by
    app-text/hunspell:0/1.7= required by (kde-frameworks/sonnet-5.59.0:5/5.59::kde-kit, installed)
                     ^^^^^^^                                                                       
    (and 1 more with the same problem)
NOTE: Use the '--verbose-conflicts' option to display parents omitted above
It may be possible to solve this problem by using package.mask to
prevent one of those packages from being selected. However, it is also
possible that conflicting dependencies exist such that they are
impossible to satisfy simultaneously.  If such a conflict exists in
the dependencies of two different packages, then those packages can
not be installed simultaneously. You may want to try a larger value of
the --backtrack option, such as --backtrack=30, in order to see if
that will solve this conflict automatically.
For more information, see MASKED PACKAGES section in the emerge man
page or refer to the Gentoo Handbook.
Thanks!

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

Hey Everyone,
We have a new FAQ developed that allows you to more easily browse answers. See:
https://www.funtoo.org/FAQ
You can also submit your own FAQ questions which I will answer! ? Hope you enjoy it.
Best,
Daniel

Hello to everybody & sorry for my poor english.
I really wish to ask the comunity of Funtoo:
Why you are staying on GitHub,scince it was acquired by the Sionistic/Massonic microsoft?
Are you not affraid,that someone can manipulate your sources to realese some kind of backdoor in your images ?
Thanks . 

OK, done.... ?

Thanks for adding the 2FA to the site.  I wish more would do it.  I use it every where I can.  Even my home server has the google-auth pam modules for ssh.

There is nothing wrong with some branches having "detached head". You will see this when there has been a recent update to our 1.3 development branch.
If you see this at the end:
Sync successful and kits in alignment! :) Then it means things are OK.

May I ask what your system's
eselect python show is set to? I guess python3.6.

OK, I 've set to python3.6 via
root@carbon nik # eselect python list Available Python interpreters, in order of preference: [1] python3.4 [2] python2.7 [3] python3.6 (fallback) [4] python3.5 (fallback) root@carbon nik # eselect python set 3 root@carbon nik # eselect python show python3.6 and it worked.  Thank you for the hints!

since the commands from boot-update moved to ego you need to remove boot-update first.
 

The Funtoo authentication system has recently been upgraded to use Authy, a SMS-based verification service. We're using this to protect the funtoo community against spam bots and other nasty things, which are unfortunately an issue we need to deal with.
You will not be able to log in to Funtoo until you upgrade your account!
To do this, go to https://auth.funtoo.org/login, log in, and you will be prompted to provide an SMS number to verify your account.
This will only happen once -- it normally happens upon account registration only -- but existing Funtoo users will need to go through this extra step.
Apologies for the inconvenience, but unfortunately this kind of thing is becoming necessary.
Best,
Daniel

is in the /var/db/pkg/app-crypt/qca-2.1.3-r2/qca-2.1.3-r2.ebuild
before has qt4 and qt5 IUSE , now have no!
PS: if u remove kdelibs your kde goes broke!!!!

yes, I know that one exactly.
...
Once it will be fixed :)

Hi All,
xorg-kit 1.19-prime will be the default after the next tree update. It includes xorg-server-1.19.3 but with backports of all security fixes through (and including) xorg-server 1.19.5.

yes
you can save the distfiles and pkgs (binary) if its a problem, otherwise /usr/portage can be zapped

http://blog.chromium.org/2014/05/update-on-npapi-deprecation.html
I just tried the Java verification site https://www.java.com/verify/ and the applet does not work for me with chromium 38.0.2125.24. It does work with firefox 31.0 and oracle-jdk-bin 1.7.0.67.

To compile this version of chromium you have upgrade gcc-5.3.0-r1 to gcc-5.4.0. Look here: https://bugs.funtoo.org/browse/FL-4235. sys-devel/gcc-5.4.0 is sufficient to complile this version of chromium.

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.

and from my own experience, i have never used stable builds anywhere and there was no really major problems (like disastrous ones), maybe 2-3 only in last 10 years. so, a key is - when you know what to do with stable or unstable - you could expect things to work. if you don't know what to do, likely you'll trap into troubles regardless stable or unstable used. Sometimes updates can be frustrating, i agree. And for newcomers, of course, it's hard as they mostly driven by existing documentation, web, irc -which can be really wrong. The "stable" is what is controlled by matter of letter, in ebuilds, i can put "amd64" instead "~amd64" and it will be considered stable by package manager, which is of course far from real definition of stable. For example, back into not so old case (about 4 monthes), xorg-server-1.19 stabilized by gentoo, due to multiple security vulnerabilities in xorg itself and in it's core parts. xorg-1.19, in turn, found to be very unstable in certain conditions, so the security fixes diminished by the fact you have no working xorg. Those security fixes can be easily, and they are in Funtoo, backported into good known 1.17 version. of course, if 1.19 were ok for the one, he could choose using 1.19. Just trying to describe that stabilization and stable by means of packages, is a volatile term.

I don't use Docker, so can't answer concerning it.
 
When you run "make menuconfig", when you save and close, it moves .config to .config.old. So just run:
diff /usr/src/linux/.config /usr/src/linux/.config.old You can't show changes with menuconfig, and copy the text with markings (whatever markings are).

Hi everyone,
 
We've decided to retire funtoo-stable to keep us focused as we move towards funtoo kits and other next-generation initiatives. I recommend that all stable users migrate to funtoo-current.