Jump to content

Search the Community

Showing results for tags 'ego'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Funtoo Discussion Forums
    • News and Announcements
    • General Discussion
    • Dev Central
    • Funtoo Hosting
    • Funtoo Infrastructure
  • Help Central
    • General Help
    • Installation Help
    • Portage Help
    • Desktop Help
    • Server Help
  • Funtoo Services

Blogs

  • drobbins' Blog
  • It's a Bear's life
  • haxmeister's Blog
  • psychopatch's Blog
  • 666threesixes666's Blog
  • decision theory
  • Chris Kurlinski's Blog
  • Sandro's Blog
  • danielv's Blog
  • Not So Stupid Admin Tricks
  • maldoror's Blog
  • andreawilson's Blog
  • Simple Step-by-Step Server Setup
  • saraedward's Blog
  • eusanpe
  • Linux Container Club - LXD/LXC's Blog
  • Funtoo Perl Hackers's Perl on Funtoo

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


freenode


github


web


First Name


Last Name


Location


Interests

Found 23 results

  1. Sync successful and kits in alignment! :) Updating /etc/portage/repos.conf... Updating profiles at /etc/portage/make.profile/parent... Updating non-funtoo repositories... !!! Unable to parse profile: '/etc/portage/make.profile' !!! ParseError: Parent '/var/git/meta-repo/kits/core-kit/profiles/funtoo/1.0/linux-gnu/build/experimental' not found: '/etc/portage/make.profile/parent' Can't understand where the issue is coming from. The `parent` file has this content: core-kit:funtoo/1.0/linux-gnu/arch/x86-64bit core-kit:funtoo/1.0/linux-gnu/build/experimental core-kit:funtoo/1.0/linux-gnu/arc
  2. Hello, I was going finally to update my ego profile to 1.3 following this guide: https://www.funtoo.org/Upgrade_Instructions/1.3-release I've followed every step and checked that it worked as intended. I've just done the this step now (succesfully): emerge -auDN @system --ignore-world Now, the next step would to to run emerge -auDN @world But this one, it fails spectacularly... These are the packages that would be merged, in order: Calculating dependencies .. ....... ...... ...... done! [ebuild U ] x11-misc/util-macros-1.19.2-r1 [1.19.1] [ebuild
  3. So I got the 11-20 stage3 for Haswell, removed /lib43,/usr/lib32, and /usr/src/lib32, removed lib32 from env.d and generated a new ld.so.conf. I had to emerge sys-kernel/{debian-sources-lts, genkernel, linux-firmware}, sys-firmware/intel-micocode, sys-apps/iucode_tool, and grub. This gave me a working Core, so (after a backup) I ran 'epro flavor desktop'. I was required to emerge dev-python/{pygments, pyyaml} [could this be included in desktop flavor?], and eselect fontconfig to add 60-liberation.conf (for some reason). Now the 'genkernel all' is failing on gnupg. I tried emerging ap
  4. I was trying to update my Funtoo Virtual Container ( https://www.funtoo.org/Funtoo_Containers ) that I had been lacks in keeping up to date (everything was working fine). Now I've dug myself a deep hole that I need help getting out of. First I did a eix-sync (ego sync) which lead to a error report very similar to the one in this bug report, that is closed yet has people still showing the same problem: https://bugs.funtoo.org/browse/FL-5504?page=com.atlassian.jira.plugin.system.issuetabpanels%3Aall-tabpanel I tried to recompile ego as the bug report : https://forums.
  5. ego sync gives a couple of "errors". Some of the kit repositories are "behind" and don't get updated: Syncing meta-repo M kits/core-hw-kit M kits/core-kit M kits/desktop-kit M kits/dev-kit M kits/editors-kit M kits/games-kit M kits/gnome-kit M kits/haskell-kit M kits/java-kit M kits/kde-kit M kits/lang-kit M kits/lisp-scheme-kit M kits/llvm-kit M kits/media-kit M kits/ml-lang-kit M kits/net-kit M kits/nokit M kits/perl-kit M kits/php-kit M kits/python-kit M kits/
  6. I am upgrading my system, after some time, and I have: root@carbon nik # eix -I app-admin/ego [?] app-admin/ego Available versions: 2.4.2^m **2.5.0.2^m **2.5.0.4 **9999^m {zsh-completion PYTHON_SINGLE_TARGET="python3_4 python3_5 python3_6 python3_7" PYTHON_TARGETS="python3_4 python3_5 python3_6 python3_7"} Installed versions: 2.6.3(08:56:07 PM 11/01/2018)(-zsh-completion PYTHON_SINGLE_TARGET="python3_6 -python3_4 -python3_5 -python3_7" PYTHON_TARGETS="python3_6 -python3_4 -python3_5 -python3_7") Homepage: http://www.funtoo.org/Package:Ego Description:
  7. Tried to sync this afternoon to get caught up and was greeted with this: ego sync Syncing meta-repo fatal: Couldn't find remote ref refs/heads/1.2 error: pathspec '1.2' did not match any file(s) known to git. error: pathspec 'python-kit' did not match any file(s) known to git. error: pathspec '=' did not match any file(s) known to git. error: pathspec '3.6-prime-release' did not match any file(s) known to git. HEAD is now at 1261139 kit updates Skipping repository kits/python-modules-kit/ fatal: Couldn't find remote ref refs/heads/1.2 ERROR: There was an error syncing meta-repo. tried d
  8. ego-2.6.0 released with lot of fixes. This version now also incorporates the boot-update, which was previously a standalone package. To update to new version of ego following steps required: # ego sync # emerge --deselect boot-update # emerge -auDN @world
  9. I followed the instructions in this thread: Now after running "ego sync" and "emerge -auND @world" when I run "emerge -cp" I get the following output: >sudo emerge -cp Password: * Always study the list of packages to be cleaned for any obvious * mistakes. Packages that are part of the world set will always * be kept. They can be manually added to this set with * `emerge --noreplace <atom>`. Packages that are listed in * package.provided (see portage(5)) will be removed by * depclean, even if they are part of the world set. * * As a safety measure, depclean will no
  10. I mount meta-repo as read only to lxd container. If I run "ego sync" it crushes: # ego sync ERROR: Ego encountered an unexpected error: OSError ERROR: Full traceback written to /tmp/ego-traceback-3362.txt. # cat /tmp/ego-traceback-3362.txt [Errno 30] Read-only file system: '/var/git/meta-repo/.touch'Traceback (most recent call last): File "/usr/bin/ego", line 120, in <module> EgoModule.run_ego_module(action, econfig, args, VERSION) File "/usr/share/ego/python/ego/module.py", line 102, in run_ego_module ego_module(*args) File "/usr/share/ego/python/ego/module.py",
  11. I did not update my system for a long time and also missed the announcement for the meta-repo thing. I decided to update, read a lot of links from the forums etc. and ended up screwing up my build system. (for example this post ) # epro === Enabled Profiles: === arch: base build: (not set) subarch: (not set) flavor: (not set) mix-ins: (not set) === Python kit: === branch: 3.4-prime # emerge -vpuD --newuse @world !!! /etc/portage/make.profile is not a symlink and will probably prevent most merges. !!! It should point into a profile within
  12. error when update the profile to version 1.2 and use "ego sync" the first line is uncommented "/var/git/meta-repo/kits/core-kit/profiles/base/make.defaults"
  13. Hi, I'm already using the gcc version 7.3, I wonder if I need reinstall the gcc if change the kits to version 1.2 ? or just keep the tutorial skip that step.
  14. Hi, I want to confirm that for some kits, they're no longer being actively synced with gentoo. For example, core-kit, apparently is not: The problem is that for example the version I'm trying to download doesn't exist in the gentoo package listing and is not available on mirrors. net-dns/bind-tools-9.11.0_p3:0/0::core-kit sys-apps/file-5.30 Lastly, on a related note, what is the process for marking packages as stable. Ie, is there automated testing, then someone simply updates the branch? If so, I'd like to understand the process so I could als
  15. 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 specifie
  16. Hello. After updating ego to 2.2.X it started ignoring my ego.conf and switched couple of kits to "default" branches. However I would like to stay on "master" branches, but it doesn't allow this any more. So is it some kind of planned feature? Any normal way to switch back again to master branches or just "git pull master" in kits git dirs?
  17. Ego-2.3.1 has been released, and contains a critical fix -- version 2.3.0 didn't properly update python-kit USE settings in the profile when 'epro update' was run. The new 2.3.1 version will strip old python-related USE settings and add updated settings. This could cause problems on upgrade from a non-kitted system or problems when switching python implementations.
  18. ego-2.3.0 has been released and will be appearing in the tree in the next few hours. It is currently keyword masked but is available for testing and evaluation. It should be considered beta software for end-users -- our developers will be testing it but you are free to do so as well. Several bugs have been fixed (meta-repo sync robustness, avoiding a failure when run in a root-only-readable current working directory), and in addition several unit tests have been added, the entire code base has been heavily refactored, including a completely rewritten internal API for ego profile management.
  19. ego sync Syncing meta-repo remote: Counting objects: 30, done. remote: Compressing objects: 100% (18/18), done. remote: Total 30 (delta 12), reused 30 (delta 12), pack-reused 0 Unpacking objects: 100% (30/30), done. From https://github.com/funtoo/meta-repo 5699fe0..8129545 master -> origin/master Fetching submodule kits/core-kit From https://github.com/funtoo/core-kit 366dddf7..be579f3e 1.0-prime -> origin/1.0-prime 1190769b..1b579e36 1.1-prime -> origin/1.1-prime Fetching submodule kits/editors-kit From https://github.com/funtoo/editors-kit 3fe6e8f..efee095 mast
  20. Hi, just ran ego sync and got ... Syncing lang-kit branch 1.1-prime fatal: Could not change back to '/root': Permission denied Could not clone kit 'lang-kit' into '/var/git/meta-repo/kits/lang-kit'. Any help? Thanks. -- Saulius
  21. Ego-2.2.1 has been released. This release includes fixes for the accuracy of information shown by "ego kit list", a helpful informational message at the end of the "ego kit" commands, and some minor unit test improvements.
  22. Hi All, ego-2.2.0 has been released, and is an important update, and will be appearing in meta-repo soon. New functionality has been added to help you view kit configuration. To view your current kit settings, type: # ego kit status This will display your current kit settings, as well as their stability level. The stability level is set by Funtoo and lets you know if you are running something we consider 'stable' or not. We recommend that all our users use kits that have a 'prime' stability level. Note that this is different than the kit having 'prime' in its name! When I cre
  23. With the on-going change, it's expected that we, users, have several and different, difficulties. And while it is impossible to deal with all at once, I feel that one sticky thread should be there to guide. Or use only github's issues feature. Myself, have posted in various threads during the last weeks. And contribute, this way, in more noise. Apologies for that. Can we have one sticky thread for the Switch? Thank you
×
×
  • Create New...