overkill

I don't think you need the gentoo overlay. I found a bug report that says the latest xfce has been added to the funtoo tree, however, I cannot find xfce4-meta-4.12 in the tree. Maybe it was overlooked? Here's the report: https://bugs.funtoo.org/browse/FL-2162 Maybe you need to file a new bug with your issue?

Sounds like a question for ESET support. There should be some sort of init script for eset. Don't know if it has an openrc compatible init script. If it doesn't then you could probably use the /etc/local.d directory to store custom eset.start and eset.stop files. See the readme in /etc/local.d/README

If you do not the the python docs, then disable the "doc" useflag for python. I believe it's disabled by default, so you must have enabled the doc useflag globally in make.conf or specifically for python in your /etc/portage/package.use file I believe you hit a bug. If the ebuild calls for a non-existent or missing package, that package should exist in the tree. So that package probably needs to be re-added to the tree or the ebuild needs to be corrected. I think you should file a bug report on this issue at bugs.funtoo.org.

You need to boot from whatever you used to install (SysRescueCD?), chroot into the system, and set the password again. Maybe you set the password after you exited the chroot environment? If so, then the root password is unset.

So, if I want to replace CFLAGS="-march=native -O2 -pipe" in make.conf, would that be subarch 16? ... [16] funtoo/1.0/linux-gnu/arch/x86-64bit/subarch/native_64 ...

Updates completed successfully. With only >=xorg-server-1.17 masked, Gnome is functioning correctly. Perhaps >=xorg-server-1.17 should be added to the Gnome mix-in mask?

Thanks for the input. I thought it was xorg-server, but I had to mask the rest to roll back to where I was. If I now only mask xorg-server-1.17.1-r4, the other updates reappear. I'm going to give it another try with # FEATURES="-colision-protect" emerge world -uDNav --with-bdeps=y These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild N ] dev-python/beaker-1.6.4-r1000 USE="{-test}" PYTHON_ABIS="2.7 3.3 -2.6 -2.7-jython -2.7-pypy -3.1 -3.2 -3.2-pypy -3.4 (-3.5)" 0 kB [ebuild N ] dev-python/mock-1.0.1-r1000 USE="-doc {-test}" PYTHON_ABIS="2.7 3.3 -2.6 -2.7-jython -2.7-pypy -3.1 -3.2 -3.2-pypy -3.4 (-3.5)" 0 kB [ebuild N ] virtual/python-mock-0 PYTHON_ABIS="2.7 3.3 -2.6 -2.7-jython -2.7-pypy -3.1 -3.2 -3.2-pypy -3.4 (-3.5)" 0 kB [ebuild U ] sys-devel/llvm-3.6.0:0/3.6 [3.5.1:0/3.5] USE="libffi ncurses python static-analyzer xml -clang -debug -doc -gold -libedit -multitarget -ocaml {-test}" ABI_X86="(64) -32 (-x32)" PYTHON_TARGETS="python2_7 -pypy" VIDEO_CARDS="-radeon" 0 kB [ebuild N ] dev-python/mako-1.0.0-r1000 USE="-doc {-test}" PYTHON_ABIS="2.7 3.3 -2.6 -2.7-jython -2.7-pypy -3.1 -3.2 -3.2-pypy -3.4 (-3.5)" 0 kB [ebuild U ] app-admin/eselect-opengl-1.3.1-r3 [1.2.7] 0 kB [ebuild U ] x11-proto/glproto-1.4.17-r1 [1.4.17] ABI_X86="(64) -32 (-x32)" 0 kB [blocks b ] <x11-proto/glproto-1.4.17-r1 ("<x11-proto/glproto-1.4.17-r1" is blocking app-admin/eselect-opengl-1.3.1-r3) [ebuild U ] media-libs/mesa-10.5.2 [10.3.5] USE="classic dri3 egl gallium gbm gles2 llvm nptl udev -bindist -d3d9% -debug -gles1 -opencl -openmax -osmesa -pax_kernel -pic (-selinux) -vaapi% -vdpau -wayland -xa -xvmc (-openvg%) (-r600-llvm-compiler%)" ABI_X86="(64) -32 (-x32)" VIDEO_CARDS="intel (-freedreno) -i915 -i965 -ilo -nouveau -r100 -r200 -r300 -r600 -radeon -radeonsi -vmware" 0 kB [blocks b ] <media-libs/mesa-10.3.7-r2 ("<media-libs/mesa-10.3.7-r2" is blocking app-admin/eselect-opengl-1.3.1-r3) [ebuild U ] x11-base/xorg-server-1.16.4-r1:0/1.16.1 [1.16.1-r4:0/1.16.1] USE="ipv6 kdrive nptl suid udev xorg -dmx -doc -glamor -minimal (-selinux) -static-libs -systemd -tslib -unwind -wayland -xnest -xvfb" 0 kB [blocks b ] <x11-base/xorg-server-1.16.4-r1 ("<x11-base/xorg-server-1.16.4-r1" is blocking app-admin/eselect-opengl-1.3.1-r3) [ebuild U ] x11-drivers/xf86-input-evdev-2.9.2 [2.9.1] 0 kB [ebuild U ] x11-drivers/xf86-input-synaptics-1.8.2 [1.8.1] 0 kB Total: 11 packages (7 upgrades, 4 new), Size of downloads: 0 kB Conflict: 3 blocks Would you like to merge these packages? [Yes/No]

I rolled back to xorg-server-1.16.1-r4. That's what I had before the updates. I had to add the following to my /etc/portage/package.mask file in order to down grade: >x11-base/xorg-server-1.16.1-r4 =app-admin/eselect-opengl-1.3.1-r3 =x11-proto/glproto-1.4.17-r1 >media-libs/mesa-10.3.5 =x11-drivers/xf86-input-evdev-2.9.2 =x11-drivers/xf86-input-synaptics-1.8.2 >sys-devel/llvm-3.5.1 Then I used # emerge -C eselect-opengl -a # FEATURES="-colision-protect" emerge xorg-server -1av to roll back xorg-server. Gnome is functioning correctly again. Here's the output of ck-list-sessions: # ck-list-sessions Session4: unix-user = '1000' realname = 'Joe Derp' seat = 'Seat1' session-type = '' active = TRUE x11-display = ':0' x11-display-device = '/dev/tty7' display-device = '' remote-host-name = '' is-local = TRUE on-since = '2015-03-30T17:46:16.216036Z' login-session-id = '2' Seems these updates aren't ready to be rolled out for Gnome Desktops. I filed this bug: https://bugs.funtoo.org/browse/FL-2232

Have you tried rolling back xorg-server to the previous version?

I forgot to mention that using the alt key to change the menu and show the suspend/hibernate options also does not function. I found this bug https://bugs.funtoo.org/browse/FL-2229 that I experienced. I don't know if it has anything to do with this particular issue. I've reinstalled those packages with FEATURE="-collision-protect", but I can't test it out yet.

My gnome was working fine, until the last group of updates. After that, DPMS only blanks the screen - the backlight stays on as does the mouse cursor. The shutdown / reboot option has now disappeared from the the menu. Here's the last batch of updates: Sun Mar 29 19:27:41 2015 >>> sys-devel/gnuconfig-20150308 Sun Mar 29 19:27:53 2015 >>> media-fonts/corefonts-1-r7 Sun Mar 29 19:27:59 2015 >>> app-misc/pax-utils-1.0.3 Sun Mar 29 19:28:05 2015 >>> dev-python/beaker-1.6.4-r1000 Sun Mar 29 19:28:10 2015 >>> dev-python/mock-1.0.1-r1000 Sun Mar 29 19:28:14 2015 >>> virtual/python-mock-0 Sun Mar 29 19:28:19 2015 >>> dev-python/mako-1.0.0-r1000 Sun Mar 29 19:31:34 2015 >>> media-libs/mesa-10.5.2 Sun Mar 29 19:32:27 2015 >>> x11-base/xorg-server-1.17.1-r1 Sun Mar 29 19:32:49 2015 >>> x11-drivers/xf86-video-intel-2.99.917 Sun Mar 29 19:32:59 2015 >>> x11-drivers/xf86-input-synaptics-1.8.1 Sun Mar 29 19:33:09 2015 >>> x11-drivers/xf86-input-evdev-2.9.1 Sun Mar 29 19:33:17 2015 >>> x11-drivers/xf86-input-mouse-1.9.1 Sun Mar 29 19:33:26 2015 >>> x11-drivers/xf86-input-keyboard-1.8.0 Sun Mar 29 19:33:38 2015 >>> app-emulation/emul-linux-x86-opengl-20140508-r1 Sun Mar 29 19:34:06 2015 >>> x11-drivers/nvidia-drivers-349.12 Sun Mar 29 19:34:30 2015 >>> app-admin/sudo-1.8.13

AFAIK, the CPU_FLAGS_X86 variable is for ebuilds that contain the option for those flags whereas the CHOST, CFLAGS and CXXFLAGS are for EVERY ebuild. If you want to see what would be recompiled, add the result that you posted in your make.conf file, and run a --pretend emerge: `emerge world -uDNpv --with-bdeps=y` IIRC, it was only about 22 packages on my setup.

Thank you for clarifying, Oleg.

IMHO it would be wise to use portage's news feature for something like this. I just happened to come here and find it, but it would have been useful to see a new news item was available after syncing and then view it with `eselect news read`. Or has the news feature been deprecated?

app-portage/genlop is another good tool to have installed to investigate updates/installs/removals of ebuilds.

Answering my own question, it's util-linux-2.25.2.

I ran dmesg today and was quite surprised to see that the output was colorized. I've NEVER seen that - EVER! Pretty cool! Which package is responsible? readline? util-linux?

Have you checked your S.M.A.R.T status of your drives? Corruption or bad sectors?

I think you got sidetracked. Look at the title of this post. :) I just wanted to know how to pull dead funtoo-ported ebuilds from funtoo's tree. If I had an issue that needed fixing, I'd post a bug report on b.f.o.

It was my fault. I enabled debugging at one point a year or two back, then failed to comment "ALL" the debug lines out when finished. 2.8.xx and earlier did not have any issue with it, but 2.9, 2.10 and 2.11 did.

Yes. now it looks like this... ... smtpd_banner = $mydomain ESTMP smtpd_recipient_limit = 128 smtpd_timeout = 10 soft_bounce = no #debug_peer_level = 2 #debug_peer_list = 10.0.0.10 127.0.0.1 #debugger_command = PATH=/bin:/usr/bin:/usr/local/bin:/usr/X11R6/bin xxgdb # $daemon_directory/$process_name $process_id & sleep 5 ... ...and it works as it should

Here's the first error after updating: Jan 10 14:43:06 newton postfix/smtpd[9628]: fatal: bad numerical configuration: smtpd_recipient_limit = 128 /usr/libexec/postfix/smtpd 9628 & sleep 5 Jan 10 14:43:07 newton postfix/master[9619]: warning: process /usr/libexec/postfix/smtpd pid 9628 exit status 1 Jan 10 14:43:07 newton postfix/master[9619]: warning: /usr/libexec/postfix/smtpd: bad command startup -- throttling which was triggered by this portion of main.cf: ... smtpd_banner = $mydomain ESTMP smtpd_recipient_limit = 128 #smtpd_timeout = 10 #soft_bounce = no #debug_peer_level = 2 #debug_peer_list = 10.0.0.10 127.0.0.1 #debugger_command = PATH=/bin:/usr/bin:/usr/local/bin:/usr/X11R6/bin xxgdb $daemon_directory/$process_name $process_id & sleep 5 ... The <whitespace> $daemon_directory/.... was ignored as the continuation of the line above it in 2.8.17, but later versions parsed it as a continuation of the uncommented lines above it. At first I didn't understand the log's output. Using the command `postconf smtpd_recipient_limit` showed that the $daemon_directory line was tacked on the end of the previously uncommently line, creating a bad key/value pair. newton ~ # postconf smtpd_recipient_limit smtpd_recipient_limit = 128 $daemon_directory/$process_name $process_id & sleep 5 Placing a # before the <whitespace> $daemon_directory line corrects the issue. Weird, since this main.cf file has been like that for a couple of years and never had that problem.

mail-mta/postfix-2.8.17. I had some issues that I didn't have time to troubleshoot and I wanted to keep this version in my local overlay. No need now. I finally spent the time to correct my problems and get 2.11.3-r2 working. One big problem was that I had a line beginning with whitespace in main.cf that was ignored in earlier versions of postfix, but 2.9, 2.10 and 2.11 parsed that line causing the fatal error and throttling. Took me a while to find the culprit. It would be nice if one could gather the files necessary from a dead funtoo custom ebuild and add them to one's local overlay.

Yes, I already use the "show dead files" function on s.g.o., and I understand NOT to do it in the /usr/portage directory. I already have a local overlay. Occasionally I will have the need to keep a "dead" ebuild in my local overlay tree. I usually can get all the files from s.g.o. but not if it is a forked funtoo ebuild with it's own patch files. How would one find, list and obtain/download funtoo's "dead files"?

Is there a way to pull dead ebuilds (no longer in Funtoo tree) from funtoo git? I can access dead gentoo ebuilds and files from sources.gentoo.org. Is there any way to access and download dead funtoo-ported ebuilds from funtoo's git tree?