Jump to content
funtoo forums

Leaderboard


Popular Content

Showing content with the highest reputation since 12/12/2017 in all areas

  1. 8 points
    Hi All, In order to have more predictability for users, Funtoo Linux is going to adopt a six-month release schedule starting in 2018. Our kits are currently at 1.0-prime, and we are going to skip over 1.1-prime (it didn't get done fast enough) and jump to 1.2-prime. We are going to start development on 1.2-prime today, December 28, 2017, with a planned release of the production 1.2-prime on January 21, 2018. We will then maintain the 1.2-prime kits for the next six months, until they are replaced with 1.3-prime. The schedule in detail is as follows: December, 28, 2017: start development on 1.2 January 1, 2018: we will be rolling out a python-modules-kit and perl-modules-kit as new kits (for 1.0+) January 4, 2018: Alpha release of 1.2 January 11, 2018: Beta release of 1.2 We will have a release candidate when we feel we are ready, with a scheduled production release on January 21, 2018. On February 1, 2018, the 1.0-prime kits will be deprecated and users will be migrated to the 1.2-prime kits (this should be seamless unless you've hard-coded 1.0 or 1.1-prime kits in ego.conf.) For 1.2-prime, what we are going to attempt to deliver is a default gcc of 6.4 and all ebuilds updated to be in sync with Gentoo as of January 2018. We will be using a 'current' (non-snapshotted tree) until around January 4th when we will freeze the tree and then will start backporting security fixes and updates. In a few hours, the 1.2-prime kits will appear but will be tagged as DEVELOPMENT quality, so they should not be used until they are made default. I will post updates here on our progress. Regards, Daniel
  2. 7 points
    drobbins

    1.2 Funtoo Linux Release

    Hi All, The Funtoo Linux 1.2 release is now available for use. Many of us are now running Funtoo Linux 1.2. Here's how to upgrade your system to Funtoo Linux 1.2. Note that soon, 1.2 will be the "default" version of Funtoo Linux. For now, you need to perform certain steps to switch over. We're doing this so that power users can switch over right away, and so we can make things a lot easier for less-experienced users to upgrade to Funtoo Linux 1.2. One of the features I have been working on behind-the-scenes is an "easy upgrade" functionality for ego, to perform big updates automatically. This functionality is not yet ready, but is being worked on. When this "easy upgrade" functionality is ready, 1.2 will be released via "easy upgrade" to systems who have not yet upgraded. For now, power users can upgrade by performing the following steps. First, select the new kits in your /etc/ego.conf: [kits] core-kit = 1.2-prime security-kit = 1.2-prime kde-kit = 5.12-prime media-kit = 1.2-prime java-kit = 1.2-prime ruby-kit = 1.2-prime haskell-kit = 1.2-prime lisp-scheme-kit = 1.2-prime lang-kit = 1.2-prime dev-kit = 1.2-prime desktop-kit = 1.2-prime Then, perform the following steps, as root: # ego sync This will activate the new kits. Now, if you have a /etc/portage/repos.conf/funtoo symlink, remove it: # rm /etc/portage/repos.conf/funtoo Next, # emerge -u1 gcc This will upgrade gcc. Next, # emerge -u1 glibc libnsl libtirpc rpcsvc-proto Glibc will now be upgraded. Next, # emerge -auDN @system This will upgrade your core system set of packages. Next, # emerge -auDN @world This will upgrade all other packages. Next, # emerge @preserved-rebuild This will rebuild packages that are linked to old libraries. Now, final step: # revdep-rebuild --library 'libstdc++.so.6' -- --exclude sys-devel/gcc This will rebuild all remaining packages that need to be linked against the new libstdc++. At this point, you are now upgraded to Funtoo Linux 1.2! Please report any bugs to https://bugs.funtoo.org and let us know of any issues you experience, either as part of the upgrade, related to dependencies, or related to functionality on your upgraded system. Best, Daniel Robbins
  3. 4 points
    drobbins

    New fastpull distfile service

    Hi All, Thanks to funtoo supporters, we now have a new fast download service that is available for everyone. Upgrading to the latest portage-2.3.25_beta2 will enable this service. The fastpull service consists of a lot of different moving parts, but it adds up to distfiles downloading very fast and being available. Here's how it works. When we regenerate meta-repo and kits, ebuilds are scanned for new SRC_URI tarballs, etc. These new distfiles are queued for download. Our fastpull spider then downloads these distfiles automatically, and uploads them to Google Cloud Storage. When you try to download a SRC_URI, you hit https://fastpull-us.funtoo.org first, which redirects you to the download on fast Google Cloud Storage. The design of fastpull is to ensure that all distfiles are always available going forward. It will also help us to identify situations where for some reason or another we are missing a distfile for download, although these situations should happen less and less frequently (and hopefully disappear) now that fastpull is deployed. Best, Daniel Robbins
  4. 2 points
    palica

    How do I ask a good question?

    We’d love to help you. To improve your chances of getting an answer, here are some tips: Search, and research ...and keep track of what you find. Even if you don't find a useful answer elsewhere on the site, including links to related questions that haven't helped can help others in understanding how your question is different from the rest. Write a title that summarizes the specific problem The title is the first thing potential answerers will see, and if your title isn't interesting, they won't read the rest. So make it count: Pretend you're talking to a busy colleague and have to sum up your entire question in one sentence: what details can you include that will help someone identify and solve your problem? Include any error messages, key APIs, or unusual circumstances that make your question different from similar questions already on the site. Spelling, grammar and punctuation are important! Remember, this is the first part of your question others will see - you want to make a good impression. If you're not comfortable writing in English, ask a friend to proof-read it for you. If you're having trouble summarizing the problem, write the title last - sometimes writing the rest of the question first can make it easier to describe the problem. Examples: Bad: Is there command to do what it needs? Good: How can I apply changes proposed by emerge? Bad: Problem update system Good: Why does the compile of dev-libs/boost-1.63.0 fail with x86_64-pc-linux-gnu-g++: internal compiler error: Killed (program cc1plus)? Introduce the problem before you post any code In the body of your question, start by expanding on the summary you put in the title. Explain how you encountered the problem you're trying to solve, and any difficulties that have prevented you from solving it yourself. The first paragraph in your question is the second thing most readers will see, so make it as engaging and informative as possible. Help others reproduce the problem Not all questions benefit from including code. Here are some guidelines: Include just enough code to allow others to reproduce the problem. For portage errors include all the relevant info and output. Include all relevant tags Try to include a tag for the language, library, and specific API your question relates to. If you start typing in the tags field, the system will suggest tags that match what you've typed - be sure and read the descriptions given for them to make sure they're relevant to the question you're asking! See also: What are tags, and how should I use them? Proof-read before posting! Now that you're ready to ask your question, take a deep breath and read through it from start to finish. Pretend you're seeing it for the first time: does it make sense? Try reproducing the problem yourself, in a fresh environment and make sure you can do so using only the information included in your question. Add any details you missed and read through it again. Now is a good time to make sure that your title still describes the problem! Post the question and respond to feedback After you post, leave the question open in your browser for a bit, and see if anyone comments. If you missed an obvious piece of information, be ready to respond by editing your question to include it. If someone posts an answer, be ready to try it out and provide feedback! Look for help asking for help In spite of all your efforts, you may find your questions poorly-received. Don't despair! Learning to ask a good question is a worthy pursuit, and not one you'll master overnight. Here are some additional resources that you may find useful: Writing the perfect question How do I ask and answer homework questions? How to debug small programs Meta discussions on asking questions How to ask questions the smart way — long but good advice.
  5. 2 points
    Oleg Vinichenko

    ZFS-0.7.9 added

    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
  6. 2 points
    Hi All, We have deployed our second-generation compute infrastructure and have begun the process of moving containers over to it. This funtoo-based infrastructure is running on faster hardware and is using ZFS for storage. For more information on our second-generation platform, see https://www.funtoo.org/Funtoo_Containers Also note that plans have been upgraded. Our base plan for $15/mo now comes with 8 cores and 60GB of storage (was 6 cores and 50GB previously.) The medium plan now has 16 cores and 120GB of storage (was 12 cores and 100GB). And our large plan now has 32 cores and 240GB of storage (was 24 cores and 200 GB). All existing containers will be automatically upgraded to these new resource levels when they are migrated to the new infrastructure :) Best, Daniel
  7. 2 points
    Oleg Vinichenko

    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. 2 points
    I'd rather it be opt-in, myself. One of the main reasons for my using Linux over other OS's is that data is specifically NOT sent by default.
  9. 2 points
    drobbins

    Welcome to the new forums!

    Hey all, welcome to the new forums! Our old forum software has been upgraded to the latest version and I'm going to be working hard to help make this a really great resource for everyone. Our "Funtoo Universe" section is set up in a traditional forum style, and "Help Central" is now in a Q&A-style mode. Let me know how you like the Q&A style mode. Both sets of forums allow you to tag posts as being answered and we have the ability to flag the best answer.
  10. 1 point
    jhan

    I'm not able to emerge world.

    I would guess that the system wants to enable the USE flag curl_ssl_nss for the package curl because the USE flag nss is set for the package liboauth. I get the same error when I want to reinstall liboauth. It seems that ths USE flag nss got activated by the system lately. There are not many packages that use the USE flag nss. So, if you don't need this USE flag then you could deactivate it globally or for liboauth only and you should be fine.
  11. 1 point
    is in the /var/db/pkg/app-crypt/qca-2.1.3-r2/qca-2.1.3-r2.ebuild before has qt4 and qt5 IUSE , now have no! PS: if u remove kdelibs your kde goes broke!!!!
  12. 1 point
    yes, I know that one exactly. ... Once it will be fixed :)
  13. 1 point
    Could i see your /etc/ego.conf ? I'm on 1.2ß > [ebuild R ] media-gfx/exiv2-0.26_p20171104-r1 USE="nls png xmp -doc -exampl es -webready" ABI_X86="32 (64) (-x32)" Anyway i think you're not with 1.2ß kits. If You're with 1.1, i think that you can upgrade your system to 1.2ß .... To make it possible, You can use the howto ^^ I reccomend >=gentoo-sources [experimental] 4.16.8 to have a patched kernel vs "Meltdown" & "Spectre" without graphical troubles if you'll use GNome3 desktop.
  14. 1 point
    jhan

    About blender-2.7.9

    Well, if you want blender to compile with opencl enabled but are getting an error, you could search the internet for a solution or post the build log. Maybe someone here can use the error message to help you.
  15. 1 point
    Oleg Vinichenko

    Cinnamon and Xinerama

    enabled in cinnamon for now.
  16. 1 point
    Thanks again, it solved the issue.
  17. 1 point
    5.12 branch released now
  18. 1 point
    i installed Runit i posted a video in the general discussion section. its really nice!!
  19. 1 point
    Sandro

    Use or not of Make.conf file

    I use make.conf; I started to write it in 2010 using Gentoo; then I use it also if may be "redundant" about some use flags; and i've a lot of USE and ~ 2000 ebuilds installed. Cause i like to have as more as possible the status and configuration of my system under my eyes :)
  20. 1 point
    changing /etc/boot.conf to this should work boot { generate grub default "Funtoo Linux genkernel" timeout 3 } "Funtoo Linux" { kernel bzImage[-v] } "Funtoo Linux genkernel" { kernel kernel-debian-sources-x86_64[-v] initrd initramfs-debian-sources-x86_64[-v] params += real_root=auto rootfstype=auto } "memtest86+" { type linux16 kernel /memtest86.bin }
  21. 1 point
    Oleg Vinichenko

    debian-sources-4.14.2 update

    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.
  22. 1 point
  23. 1 point
    Hi All, Coming in the next regen of meta-repo are ebuilds and supporting tools for configuration of Razer (https://www.razerzone.com/) keyboards and mice. This allows you to create neat glowy and color effects, as well as do other useful things. To configure your Razer devices, first perform the following: # emerge polychromatic # reboot Then, you will need to add your desktop user to the plugdev group, and then start openrazer-daemon in your personal .bash-login or .xprofile: openrazer-daemon At this point, you should be able to run polychromatic controller in your desktop environment to configure your Razer devices.
  24. 1 point
    drobbins

    New ebuild: turbovnc

    Hi All, I have just committed net-misc/turbovnc to the Funtoo tree. Turbo VNC is a very good VNC (https://en.wikipedia.org/wiki/Virtual_Network_Computing) client and server. As a client, it will allow you to connect to remote systems and is very fast and feature-rich, with a ton of security options. As a server, it integrates with X and supports VirtualGL. VirtualGL is functionality that overcomes some inherent limitations of VNC, which traditionally does not support OpenGL or forces applications to use non-hardware rendering. With VirtualGL, you can remotely access a Funtoo system with hardware-accelerated OpenGL and benefit from its GPU (graphics will render on the remote system using hardware acceleration and then the rendered images will be transmitted to your client.) Learn more about VirtualGL here: https://en.wikipedia.org/wiki/VirtualGL As a client, I've found turbovnc to be significantly faster than tigervnc, and the client has a lot of very useful configuration options -- see screenshots below. Please give the ebuild a try and let me know how it works for you.
  25. 1 point
    drobbins

    llvm-gcc + systemd ?

    We are planning to stick with OpenRC and gcc.
×