Oleg Vinichenko

New release of mysql-community available.
Version 8.0.14 fixes numerous security fixes. https://www.oracle.com/technetwork/security-advisory/cpujan2019-5072801.html#AppendixMSQL
Please pay attention to ebuild post instaaltion messages, if you setting up MySQl for the first time as emerge --config option now removed in favor of upstream and more featureful mysql_secure-installation
Report any issues you may find with package install and use cases.

Hi, everyone!
mysql-community-8.0.12 added in 1.3-release. This is Oracle's MySQL-8 major release. Please, notice, that this package cannot be installed with mysql (replacing). It also has certain incompatibilities with older  versions of mysql and databases, created.
https://dev.mysql.com/doc/relnotes/mysql/8.0/en/news-8-0-12.html

Hi, everyone!
mysql-community-8.0.12 added in 1.3-release. This is Oracle's MySQL-8 major release. Please, notice, that this package cannot be installed with mysql (replacing). It also has certain incompatibilities with older  versions of mysql and databases, created.
https://dev.mysql.com/doc/relnotes/mysql/8.0/en/news-8-0-12.html

Hi, everyone!
X.Org security update now available with version 1.19.3-r3. By default xorg-server ebuild installs the /usr/bin/Xorg binary with suid . In 1.19 it was found a regression which allowed a privilege escalation. This is now fixed with patch. More details can be found here: 
https://www.mail-archive.com/xorg-announce@lists.x.org/msg01138.html
A notice on suid USE flag. By default this USE flag is enabled and with unpatched xorg-server there is a security risk. Upstream recommendation is to disable suid USE. This can be achieved by:
echo "x11-base/xorg-server -suid" >> /etc/portage/package.use emerge -1 xorg-server This will work in most cases, when  login managers are used, such as GDM or similar. In case you are starting the X via xinit or startx, disable of suid USE may impact the X start. You can leave the suid USE turned on, as xorg-server has the vulnerability fix applied.

Hi, dear Funtoo users!
XFCE 4.13-release available for testing. Currently not default and requires following steps to update. In /etc/ego.conf enable xfce-kit 4.13:
[kits] xfce-kit = 4.13-release Followed by
ego sync and
emerge -auDN @world Log out and back into your desktop environment.

Hi, dear Funtoo users!
XFCE 4.13-release available for testing. Currently not default and requires following steps to update. In /etc/ego.conf enable xfce-kit 4.13:
[kits] xfce-kit = 4.13-release Followed by
ego sync and
emerge -auDN @world Log out and back into your desktop environment.

Following ebuilds now available for testing in Funtoo/Linux
sys-fs/zfs-0.7.9
sys-fs/zfs-kmod-0.7.9
sys-kernel/spl-0.7.9
These versions have a portion of upstream fixes and also support for newer kernels. Ebuilds added without keywords and do require manual setting of /etc/portage/package.keywords before update.
https://github.com/zfsonlinux/zfs/releases

Following ebuilds now available for testing in Funtoo/Linux
sys-fs/zfs-0.7.9
sys-fs/zfs-kmod-0.7.9
sys-kernel/spl-0.7.9
These versions have a portion of upstream fixes and also support for newer kernels. Ebuilds added without keywords and do require manual setting of /etc/portage/package.keywords before update.
https://github.com/zfsonlinux/zfs/releases

working on this problem

the proto blocks should be resolved.

enabled in cinnamon for now.

New kit, lllvm-kit now added. It consist of small numbers of ebuilds that are directly related to the sys-devel/llvm. The rationale behind this is that ebuilds for llvm had no update for very long time and are problematic to maintain due to those ebuilds were spread all over different kits. Now they are from one kit. This kit is enabled by default and involves following update steps:
ego sync emerge -C llvm:0 clang:0 emerge -1 llvm mesa emerge -auDN @world emerge @preserved-rebuild  

New kit, lllvm-kit now added. It consist of small numbers of ebuilds that are directly related to the sys-devel/llvm. The rationale behind this is that ebuilds for llvm had no update for very long time and are problematic to maintain due to those ebuilds were spread all over different kits. Now they are from one kit. This kit is enabled by default and involves following update steps:
ego sync emerge -C llvm:0 clang:0 emerge -1 llvm mesa emerge -auDN @world emerge @preserved-rebuild  

5.12 branch released now

Merry Christmas everyone!
The new debian-sources-4.14.2 release now available and will be the default kernel in stages. We hope it will work good for you. Please, report any inconveniences found with update on bugs.funtoo.org.

the problem is reported in https://bugs.funtoo.org/browse/FL-4576
the imagemagick-7 support patch is ready which will allow to remove the strict  dependency on older imagemagick and hence resolving the conflict.

the compilation stopped due to resource exhaustion, due to lack of RAM or having no swap.
 

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

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

yes

i remember this problem and will fix now

this is reflected in:
http://www.funtoo.org/News:Python_Multiplexing(And_another_Ego_update)

i believe the 2.3.8-r8 portage version supposed to fix this. please, update.

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.

this will bring meta-repo up-to-date.