Jump to content
funtoo forums

Oleg Vinichenko

Funtoo Linux Developer
  • Content count

  • Joined

  • Last visited

  • Days Won


Oleg Vinichenko last won the day on March 15

Oleg Vinichenko had the most liked content!


About Oleg Vinichenko

Recent Profile Visitors

573 profile views
  1. Migration to meta-repo, many blocked packages?

    the proto blocks should be resolved.
  2. NVIDIA drivers news

    With latest addition of nvidia-drivers, many of hardware might not be recognized due to upstream support deprecation With attempt of merging the driver on hardware that is not supported you will get the warning of following type: * ***** WARNING ***** * * You are currently installing a version of nvidia-drivers that is * known not to work with a video card you have installed on your * system. If this is intentional, please ignore this. If it is not * please perform the following steps: * * Add the following mask entry to /etc/portage/package.mask by * echo ">=x11-drivers/nvidia-drivers-391.0.0" >> /etc/portage/package.mask * * Failure to perform the steps above could result in a non-working * X setup. * * For more information please read: * http://www.nvidia.com/object/IO_32667.html Please, pay attention to the message and your hardware listed in in: http://www.nvidia.com/object/IO_32667.html
  3. Cinnamon and Xinerama

    enabled in cinnamon for now.
  4. Cinnamon and Xinerama

    this USE need set in the mix-in.
  5. this is incorrect, because even if clang compiler used, it uses gcc headers and it's standard library. In reporter comment, it is gcc-6.4 installed likely on his box. chromium need the patches (again) to be able to build with gcc-5
  6. python-kit/3.4-prime not found

    this is reported already https://bugs.funtoo.org/browse/FL-4940
  7. LLVM updates

    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
  8. [SOLVED] Blocked Packages because of me

    yes. this is already reported acpilight appears better alternative to xbacklight https://bugs.funtoo.org/browse/FL-4514

    it doesn't break anything python-3.6 need selected eselect python list should be set to python-3.6 emerge -auND @world need ran after setting python-3.6 kit some additional steps might be required to complete update.

    they are not unstable. Why are they? I suggest moving to python-3.6
  11. kde 5.12 update added for testing

    5.12 branch released now
  12. provide full emerge output, please.
  13. this needs reflected in wiki guides. Or, maybe fixed in ebuilds.
  14. kde-kit 5.12 branch now available for quick testing. This will bring regression fixes found recently and will sort bunch of other KDE bugs reported. It is currently in BETA state but will be default quickly. To help testing, please follow this steps: Edit /etc/ego.conf and add at bottom of the file kde-kit = 5.12-prime Save file and run ego sync. This will sync the meta-repo with new ebuilds for testing. Kind regards, Oleg.
  15. [SOLVED] modules_install fails in chroot

    you, perhaps, used a specifically optimized stage3 for the chroot? if cpu's are different, using generic_64 stage would be best choice.