dhudson

well I thought you had python target in make.conf. ( what I had to do ) but I found this post http://forums.funtoo.org/topic/1210-new-install-broken-builds-and-blocked-install/

did you update ego yet? should be 2.0.9 I think.. try emerge -1 app-admin/ego then you can use: ego sync to synchronize the portage tree may be that then you need to update your portage but updating ego worked for me.

Hi, I think you should read this and follow the Using Meta-Repo. https://github.com/funtoo/meta-repo

Hi , I'm not 100% sure but I think its telling you , you can not have both at the same time. so do a emerge --depclean mysql -a to see what its going to remove then answer y if you want it. then you should be able to proceed with your 5.5 install. notice 5.5.57 has been marked unstable for some reason.

I first did this instructions here: https://github.com/funtoo/meta-repo then tried the kits manual bump http://www.funtoo.org/News:Kits_Are_Go_(And_Ego_Needs_a_Manual_Bump) I had ego 1.01 i think an old one? I was trying to update ego is when I got the whole missing python target variable. putting the python_targets in make.conf was just a test but it worked. I commented out the python targets in make.conf and emerged dev-python/appi and it went without error. so everything seems ok now. thanks all, dave edit: IMO doing the ego bump should of come first, my fault for not keeping up:-)

UPDATE: I got ego to update by putting python targets and single target in make.conf emerge update works now and there are lots of updates and downgrades. is it safe to proceed?

/boot is not automatically mounted by default but was by genkernel, will have to put mount point in fstab i think. or do a manual mount when needed. dave

hey thanks, Cardinal here is that result lex dave # echo "dev-python/appi PYTHON_TARGETS: -* python3_4" >> /etc/portage/package.use lex dave # emerge -1av ego These are the packages that would be merged, in order: Calculating dependencies... done! !!! The ebuild selected to satisfy "dev-python/mwparserfromhell[python_targets_python3_4(-)?,python_targets_python3_5(-)?,python_targets_python3_6(-)?,-python_single_target_jython2_7(-),-python_single_target_pypy(-),-python_single_target_pypy3(-),-python_single_target_python2_7(-),python_single_target_python3_4(+)?,python_single_target_python3_5(+)?,python_single_target_python3_6(+)?]" has unmet requirements. - dev-python/mwparserfromhell-0.5::python-kit USE="" PYTHON_TARGETS="-python2_7 -python3_4 -python3_5 -python3_6" The following REQUIRED_USE flag constraints are unsatisfied: any-of ( python_targets_python2_7 python_targets_python3_4 python_targets_python3_5 python_targets_python3_6 ) (dependency required by "app-admin/ego-2.0.9::core-kit" [ebuild]) (dependency required by "ego" [argument]) Why: mwparser seems to be a media wiki parser is that right?

thanks, I did see that update and tried but I seem to have a python issue since doing the meta-repo.

So I guess this is unresolved? I seem to be in the same boat. update: "Run ". /etc/profile" to update the variable in your shell. seemed to fix this in case anyone else finds this.

Have put off all the latest changes , Calculating dependencies... done! !!! The ebuild selected to satisfy "dev-python/appi:0/0.1[python_targets_python3_4(-)?,python_targets_python3_5(-)?,python_targets_python3_6(-)?,-python_single_target_jython2_7(-),-python_single_target_pypy(-),-python_single_target_pypy3(-),-python_single_target_python2_7(-),python_single_target_python3_4(+)?,python_single_target_python3_5(+)?,python_single_target_python3_6(+)?]" has unmet requirements. - dev-python/appi-0.1.2::python-kit USE="" PYTHON_TARGETS="-python3_4 -python3_5 -python3_6" The following REQUIRED_USE flag constraints are unsatisfied: any-of ( python_targets_python3_4 python_targets_python3_5 python_targets_python3_6 ) (dependency required by "app-admin/ego-2.0.9::core-kit" [ebuild]) (dependency required by "ego" [argument]) lex meta-repo # ego sync Ego module sync does not exist. emerge -1 --nodeps ego * ego-2.0.9.tar.gz SHA256 SHA512 WHIRLPOOL size ;-) ... [ ok ] * No Python implementation selected for the build. Please set * the PYTHON_SINGLE_TARGET variable in your make.conf to one * of the following values: * * python3_4 python3_5 python3_6 seems to indicate I need to add python target in make.conf but also seems to contradict this http://www.funtoo.org/News:Python_Multiplexing(And_another_Ego_update) as usual I seem to be missing something here:)

hey thanks, cardinal. that took care of it. dave

Hi, I am not sure if this classifies as a bug or not, since monday's sync and update , guessing openrc this started. I can create the file manually , modules are already loaded. I guess its udev that takes care of /dev files but something has changed because was not a problem until Monday. any ideas welcome. thanks, dave

ok figured it out, simply emerge debian-sources-4.5.2 did the trick as a bonus fixed my X problem. dave

hello,. I have noticed since last updates , gcc, llvm kernel 4.8.15 X is not wanting to die when closing out of fluxbox. system is "current", and up to date. i get this in dmesg: [ +0.000095] WARNING: CPU: 0 PID: 4375 at /var/tmp/portage/sys-kernel/debian-sources-4.8.15/work/linux-4.8.15/drivers/gpu/drm/i915/intel_display.c:13712 [ +0.000003] pipe A vblank wait timed out [ +0.000001] Modules linked in: ctr(E) ccm(E) binfmt_misc(E) joydev(E) uvcvideo(E) videobuf2_vmalloc(E) videobuf2_memops(E) videobuf2_v4l2(E) videobuf2_ [ +0.000079] snd_hda_intel(E) mfd_core(E) thermal(E) wmi(E) e1000e(E) snd_hda_codec(E) parport_pc(E) snd_hda_core(E) battery(E) snd_hwdep(E) drm_kms_he [ +0.000082] CPU: 0 PID: 4375 Comm: X Tainted: G W E 4.8.15-1 #1 [ +0.000002] Hardware name: Dell Inc. Latitude E6220/00W5HN, BIOS A08 05/17/2012 [ +0.000006] 0000000000000286 0000000048a55469 ffffffff949b4d35 ffff88fba150fb10 [ +0.000007] 0000000000000000 ffffffff9467c19e 0000000000000000 ffff88fba150fb68 [ +0.000005] 0000000000000000 0000000000000000 0000000000000000 ffff88fba0e7c000 [ +0.000006] Call Trace: [ +0.000012] [<ffffffff949b4d35>] ? dump_stack+0x5c/0x77 [ +0.000009] [<ffffffff9467c19e>] ? __warn+0xbe/0xe0 [ +0.000007] [<ffffffff9467c21f>] ? warn_slowpath_fmt+0x5f/0x80 [ +0.000006] [<ffffffff946bcc5e>] ? finish_wait+0x3e/0x70 [ +0.000066] [<ffffffffc077fa8a>] ? intel_atomic_commit_tail+0xfca/0xfe0 [i915] [ +0.000005] [<ffffffff946bcef0>] ? wake_atomic_t_function+0x60/0x60 [ +0.000057] [<ffffffffc077fed8>] ? intel_atomic_commit+0x438/0x560 [i915] [ +0.000054] [<ffffffffc0528cf2>] ? drm_atomic_set_crtc_for_connector+0x92/0xf0 [drm] [ +0.000026] [<ffffffffc05f6749>] ? drm_atomic_helper_set_config+0x79/0xb0 [drm_kms_helper] [ +0.000036] [<ffffffffc05174f1>] ? drm_mode_set_config_internal+0x61/0x110 [drm] [ +0.000033] [<ffffffffc051bfee>] ? drm_mode_setcrtc+0x46e/0x540 [drm] [ +0.000028] [<ffffffffc050ed3f>] ? drm_ioctl+0x1af/0x460 [drm] [ +0.000030] [<ffffffffc051bb80>] ? drm_mode_setplane+0x1c0/0x1c0 [drm] [ +0.000009] [<ffffffff94815cbf>] ? do_vfs_ioctl+0x9f/0x5f0 [ +0.000004] [<ffffffff94802253>] ? vfs_write+0x163/0x1a0 [ +0.000005] [<ffffffff94816284>] ? SyS_ioctl+0x74/0x80 [ +0.000008] [<ffffffff94c7dd36>] ? system_call_fast_compare_end+0xc/0x96 [ +0.000005] ---[ end trace c513abca937de093 ]--- [ +10.179703] [drm:drm_atomic_helper_commit_cleanup_done [drm_kms_helper]] *ERROR* [CRTC:26:pipe A] flip_done timed out would it be possible to do emerge kernel 4.5.2 again because it was fine, if so not sure how i would do it. ps before you go googling this error its well known that intel i915 is not so great, should of been clear on this. i am wondering more about reverting back to 4.5.2 kernel with and emerge if that is even possible? thanks dave

hi cardinal, thanks for your help. I managed to sort it out I think..for now ,I did this ln -s /usr/share/zoneinfo/America/Chicago /etc/localtime bios set to utc time set /etc/conf.d/hwclock -> to utc dave

that took care of it. thank you! dave Edit, yes superblock message is gone but now my desktop thinks its GMT

hi, I wonder if anyone has noticed this on recent funtoo current installs? This is showing at boot: Superblock last write time is in the future , not able to copy it at that point. I have a few servers running stable that do not have this problem. hardware clock set to local in /etc/conf.d/hwclock localtime -> /usr/share/zoneinfo/America/Chicago seems to me a script is changing time to UTC at shutdown. thanks, dave