Jump to content
funtoo forums

drobbins

Funtoo Linux BDFL
  • Content count

    208
  • Joined

  • Last visited

  • Days Won

    59

drobbins last won the day on November 16

drobbins had the most liked content!

About drobbins

  • Rank
    Administrator

Recent Profile Visitors

419 profile views
  1. Funtoo mascot

    I think it could work.
  2. Can not sign into funtoo.bugs

    I can delete it for you. Send me a PM with details.
  3. Everything has been updated, and we have a new release out.
  4. Can not sign into funtoo.bugs

    Make sure you enter your username in *lowercase*. See if that helps.
  5. Hi All, ego-2.3.2 has been released and will show up in meta-repo soon. It is keyword-masked and is available for testing. This version has been tested quite a bit by the funtoo dev team so we expect it to be pretty solid but we want to give it a few days of testing by users before unmasking. New features and bug fixes include (please note there is an important one listed below....) Robustness fixes for partially-initialized repositories. Fix for term sizing New 'config' module for reading and setting ego.conf settings from cmdline. allow kit_depth to be specified in ego.conf. IMPORTANT CHANGE: replace /etc/portage/repos.conf with a real directory, and now ego will generate repos.conf entries for kits and keep them up-to-date for you. All files it manages and creates begin with the "ego-" prefix.
  6. Hi All, Just wanted to let everyone know that keychain 2.8.4 has been released and we have our official development repository for the project hosted on github: https://github.com/funtoo/keychain. Also welcome Ryan Harris @x48rph as the new official maintainer of keychain! This new release has been fixed to work with GPG2 and has various other fixes. You can learn more about keychain on its official landing page: https://www.funtoo.org/Keychain . Regards, Daniel
  7. instructions for switching to kits have changed

    Also note that the next release of ego will auto-generate repos.conf entries and automatically convert the symlink to a real directory.
  8. xorg-kit 1.19-prime now default

    Also note that in your /var/git/meta-repo/kits/xorg-kit directory, you will have a README.rst file with the latest info on security fixes in the kit. The 1.19-prime README.rst is also readable here (this is our original source for the README.rst that ends up in your kit): https://github.com/funtoo/kit-fixups/tree/master/xorg-kit/1.19-prime Also note that if you aren't explicitly specifying a kit for xorg-kit in /etc/ego.conf, your system will automatically switch to using the new kit. If you would like to stick with 1.17-prime for some reason, you can add this to your /etc/ego.conf: [kits] xorg-kit = 1.17-prime This is generally not recommended unless you have a specific reason to stick with 1.17-prime. We will continue to maintain 1.17-prime as well.
  9. xorg-kit 1.19-prime will be default soon

    Also note that in your /var/git/meta-repo/kits/xorg-kit directory, you will have a README.rst file with the latest info on security fixes in the kit. The 1.19-prime README.rst is also readable here (this is our original source for the README.rst that ends up in your kit): https://github.com/funtoo/kit-fixups/tree/master/xorg-kit/1.19-prime
  10. Hi All, xorg-kit 1.19-prime will be the default after the next tree update. It includes xorg-server-1.19.3 but with backports of all security fixes through (and including) xorg-server 1.19.5.
  11. Quick Stop

    Welcome back :)
  12. Hi All, Oleg is currently working on getting 1.19-prime ready to be the default xorg-kit, replacing 1.17-prime. We are adding some CVE fixes and mesa has been bumped to a non-release candidate. In the next day or so, if you do not have 1.17-prime specified in /etc/ego.conf, your xorg-kit will automatically switch over to 1.19-prime after ego sync.
  13. Trouble updating after migration to meta-repo

    Excellent! Thanks for taking the time to post here which allowed me to track down the bug in ego.
  14. Source code dependency resolving algorithm

    Yes -- the current code is fairly convoluted. It uses a depgraph to build up a dependency tree and then starts with the leaf nodes and works its way up the tree. The source code is here: https://github.com/gentoo/portage/blob/master/pym/_emerge/depgraph.py I've begun working on adding clearer documentation to the code but there is a lot more work to do on that front.
  15. Switch to Python 3.6?

    See this thread: We found a bug in ego-2.3.0 which was resulting in python USE settings not getting updated properly. Using the version from git as per my instructions will get this working for you so you can run "ego profile update" and get your profiles set up correctly. Or just emerge ego-2.3.1 when it shows up in meta-repo, soon.
×