Oleg Vinichenko

downgrade to 1.16 is the option to try.

need more details on adwifi problem. Please, clean off all your configs and follow http://www.funtoo.org/Funtoo_Linux_Installation#Wi-Fi

this issue has been resolved since 11.3.15. by removing erroneous USE requirement. Should not happen

Need more detailed description of a problem.

vlc is already forked by Funtoo for some extended time. I've masked a rdp USE flag. Currently freerdp is broken somehow, only a git versions are working.

Funtoo not using eselect news now. We prefer to use a web news. Example http://www.funtoo.org/News:New_OpenGL_management_in_Funtoo. Occasionally we can move news to make them available via eselect news but it's not a high priority. Maybe once a 2-3 monthes would be fine.

looks like it's reported, and a suggestion made in bug.

report this on bugs.funtoo.org

xfce4-mixer will work anyway.

ipython ebuilds are not coming from Gentoo tree and simple copy will not solve the problem (well, it will but not in a way we want). This is reported long time and I'll try to get a maintainer of overlay we merging ebuild from to force ipython update.

thx. Funtoo including vmware ebuilds directly from vmware-overlay but it looks this overlay is not updated to latest versions. Something to look.

your box is severely outdated. update it. Also this is fixed in cairo ebuild.

package.use file is for certain packages and it's entries should look like app-foo/bar cpu_flags_x86_avx. I suspect package.use not needed for you, remove it.

This will not look like in above example. And it's only in preparation phase. W.I.P. http://www.funtoo.org/Repository_Configuration

do you have libusb-compat package installed. Normally it should be present. what version and what version of libusb.

we are not using portage news anymore. https://bugs.funtoo.org/browse/FL-1789

Hello, everyone. The USE flags corresponding to the instruction sets and other features specific to the x86 (including x86-64) architecture are being moved into a separate USE flag group called CPU_FLAGS_X86. In order not to lose CPU-specific optimizations, users will be required to update their make.conf (and package.use) file. For example, if the following USE flags were present: USE="mmx mmxext sse sse2 sse3" Those flags need to be copied into: CPU_FLAGS_X86="mmx mmxext sse sse2 sse3" Please note that the same CPU_FLAGS_X86 variable is used both on 32-bit and 64-bit x86 (amd64) systems. When in doubt, you can consult the flag descriptions using one of the commonly available tools, e.g. ''equery uses'' from gentoolkit: equery uses media-video/ffmpeg Most of the flag names match /proc/cpuinfo names, with the notable exception of SSE3 which is called 'pni' in /proc/cpuinfo (please also do not confuse it with distinct SSSE3). To help users enable the correct USE flags, we are providing a Python script that generates the correct value using /proc/cpuinfo. It can be found in the {{Package|app-portage/cpuinfo2cpuflags}} package: emerge -1v app-portage/cpuinfo2cpuflags cpuinfo2cpuflags-x86 In order to ensure safe migration and maintain compatibility with external repositories, it is recommended to preserve the old USE settings for a period of one year or until no package of interest is still using them

mate is gnome2, cinnamon is gnome3 flavor, not much we can do about it.

that's explained in draft news, thx to Micha? G?rny. There was no real gain in such conversion, but since its implemented, here it is http://www.funtoo.org/News:CPU_FLAGS_X86

https://bugs.funtoo.org/browse/FL-1884 is the answer

yes, it's util-linux, which recently updated in Funtoo

this should be fixed with tree update.

known issue, caused by locale misbehave. Temporary fix is LC_ALL="en_US.UTF-8" emerge wicd

i have no idea, sorry. Not enough details given.

sorry, this is hard to figure :) Any details?