Jump to content
funtoo forums

Search the Community

Showing results for tags 'ego'.



More search options

  • 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

There are no results to display.

There are no results to display.


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


Location


Interests

Found 21 results

  1. 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.funtoo.org/topic/1633-more-trouble-ego-problem/ indicates and that in turn lead to "it does the same , im really really starting to hate python". Me too. Which in turn lead me to somehow screwing up my profile. Which should be a simple server profile for the Container. So I seem to have a circular breakage of my profile is broken, I need to update ego and can't because something is wrong with python in the profile. I can still compile something like eix just fine, so the system is not completely down, yet at least. It would seem I need to fix my profile, without ego, get a viable default python set in the profile, then recompile ego. Help? Please. This is the ego traceback:
  2. NikosAlexandris

    Detached HEAD state for some kit branches

    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/ruby-kit M kits/science-kit M kits/security-kit M kits/text-kit M kits/xfce-kit M kits/xorg-kit Already on 'master' Your branch is up to date with 'origin/master'. HEAD is now at 286810e kit updates Skipping repository kits/python-modules-kit/ Already up to date. Syncing core-kit branch 1.2-prime Already on '1.2-prime' Your branch is up to date with 'origin/1.2-prime'. HEAD is now at 5680cc556 updates Already up to date. Syncing core-hw-kit branch master Already on 'master' Your branch is up to date with 'origin/master'. HEAD is now at 2c1af99 updates Already up to date. Syncing security-kit branch 1.2-prime Already on '1.2-prime' Your branch is up to date with 'origin/1.2-prime'. HEAD is now at 90ee4529 updates Already up to date. Syncing xorg-kit branch 1.19-prime Already on '1.19-prime' Your branch is up to date with 'origin/1.19-prime'. HEAD is now at b756d3b3 FL-5792: add multiple CVE fixes to libxkbcommon Already up to date. Syncing gnome-kit branch 3.26-prime Already on '3.26-prime' Your branch is up to date with 'origin/3.26-prime'. HEAD is now at 3640bca8 Merge branch '3.26-prime' of git.funtoo.org:kits/gnome-kit into 3.26-prime Already up to date. Syncing kde-kit branch 5.12-prime Previous HEAD position was 966e1f4d... updates Switched to branch '5.12-prime' Your branch is behind 'origin/5.12-prime' by 13 commits, and can be fast-forwarded. (use "git pull" to update your local branch) HEAD is now at 0a864c53 updates fatal: Couldn't find remote ref refs/heads/5.10-prime Note: checking out '966e1f4d9b694acd8828d27a678f8054d8109445'. You are in 'detached HEAD' state. You can look around, make experimental changes and commit them, and you can discard any commits you make in this state without impacting any branches by performing another checkout. If you want to create a new branch to retain commits you create, you may do so (now or later) by using -b with the checkout command again. Example: git checkout -b <new-branch-name> HEAD is now at 966e1f4d... updates Syncing media-kit branch 1.2-prime Previous HEAD position was b251500e6... updates Switched to branch '1.2-prime' Your branch is behind 'origin/1.2-prime' by 34 commits, and can be fast-forwarded. (use "git pull" to update your local branch) HEAD is now at 108e9c73b updates fatal: Couldn't find remote ref refs/heads/1.1-prime Note: checking out 'b251500e6a14597e8555659bc2cc7585fddb6e84'. You are in 'detached HEAD' state. You can look around, make experimental changes and commit them, and you can discard any commits you make in this state without impacting any branches by performing another checkout. If you want to create a new branch to retain commits you create, you may do so (now or later) by using -b with the checkout command again. Example: git checkout -b <new-branch-name> HEAD is now at b251500e6... updates Syncing perl-kit branch 5.24-prime Already on '5.24-prime' Your branch is up to date with 'origin/5.24-prime'. HEAD is now at 75001926 updates Already up to date. Syncing python-modules-kit branch master Already on 'master' Your branch is up to date with 'origin/master'. HEAD is now at 28b7cb43 updates Already up to date. Syncing python-kit branch 3.6-prime Already on '3.6-prime' Your branch is up to date with 'origin/3.6-prime'. HEAD is now at 48931a6b3 updates Already up to date. Syncing php-kit branch master Already on 'master' Your branch is up to date with 'origin/master'. HEAD is now at 8538bce updates Already up to date. Syncing java-kit branch 1.2-prime Previous HEAD position was 2377d02d... updates Switched to branch '1.2-prime' Your branch is behind 'origin/1.2-prime' by 7 commits, and can be fast-forwarded. (use "git pull" to update your local branch) HEAD is now at be486998 updates fatal: Couldn't find remote ref refs/heads/1.1-prime Note: checking out '2377d02d27667e154b60db388ce27408e2a0ebab'. You are in 'detached HEAD' state. You can look around, make experimental changes and commit them, and you can discard any commits you make in this state without impacting any branches by performing another checkout. If you want to create a new branch to retain commits you create, you may do so (now or later) by using -b with the checkout command again. Example: git checkout -b <new-branch-name> HEAD is now at 2377d02d... updates Syncing ruby-kit branch 1.2-prime Already on '1.2-prime' Your branch is up to date with 'origin/1.2-prime'. HEAD is now at 6e790275 updates Already up to date. Syncing haskell-kit branch 1.2-prime Already on '1.2-prime' Your branch is up to date with 'origin/1.2-prime'. HEAD is now at 09faf7a updates Already up to date. Syncing ml-lang-kit branch 1.2-prime Already on '1.2-prime' Your branch is up to date with 'origin/1.2-prime'. HEAD is now at 4014aa9 updates Already up to date. Syncing lisp-scheme-kit branch 1.2-prime Already on '1.2-prime' Your branch is up to date with 'origin/1.2-prime'. HEAD is now at fc854bc updates Already up to date. Syncing lang-kit branch 1.2-prime Already on '1.2-prime' Your branch is up to date with 'origin/1.2-prime'. HEAD is now at d6cf666 updates Already up to date. Syncing llvm-kit branch 1.2-prime Already on '1.2-prime' Your branch is up to date with 'origin/1.2-prime'. HEAD is now at 004fcf3 updates Already up to date. Syncing dev-kit branch 1.2-prime Previous HEAD position was cc9407fcd... updates Switched to branch '1.2-prime' Your branch is behind 'origin/1.2-prime' by 40 commits, and can be fast-forwarded. (use "git pull" to update your local branch) HEAD is now at ea28874f5 updates fatal: Couldn't find remote ref refs/heads/1.1-prime Note: checking out 'cc9407fcdef7a24b4e40892e648c9a1b0de44cc2'. You are in 'detached HEAD' state. You can look around, make experimental changes and commit them, and you can discard any commits you make in this state without impacting any branches by performing another checkout. If you want to create a new branch to retain commits you create, you may do so (now or later) by using -b with the checkout command again. Example: git checkout -b <new-branch-name> HEAD is now at cc9407fcd... updates Syncing xfce-kit branch 4.12-prime Previous HEAD position was e95e659... updates Switched to branch '4.12-prime' Your branch and 'origin/4.12-prime' have diverged, and have 1 and 14 different commits each, respectively. (use "git pull" to merge the remote branch into yours) HEAD is now at 82acd2c updates *** Please tell me who you are. Run git config --global user.email "you@example.com" git config --global user.name "Your Name" to set your account's default identity. Omit --global to set the identity only in this repository. fatal: unable to auto-detect email address (got 'portage@carbon.(none)') Note: checking out 'e95e659c1e27b8425b95efd13c6eed76fb620b12'. You are in 'detached HEAD' state. You can look around, make experimental changes and commit them, and you can discard any commits you make in this state without impacting any branches by performing another checkout. If you want to create a new branch to retain commits you create, you may do so (now or later) by using -b with the checkout command again. Example: git checkout -b <new-branch-name> HEAD is now at e95e659... updates Syncing desktop-kit branch 1.2-prime Previous HEAD position was e3f44282... updates Switched to branch '1.2-prime' Your branch is behind 'origin/1.2-prime' by 26 commits, and can be fast-forwarded. (use "git pull" to update your local branch) HEAD is now at f9a96a84 updates fatal: Couldn't find remote ref refs/heads/1.1-prime Note: checking out 'e3f44282680c6d792141eb350f923ca2deddd4d1'. You are in 'detached HEAD' state. You can look around, make experimental changes and commit them, and you can discard any commits you make in this state without impacting any branches by performing another checkout. If you want to create a new branch to retain commits you create, you may do so (now or later) by using -b with the checkout command again. Example: git checkout -b <new-branch-name> HEAD is now at e3f44282... updates Syncing editors-kit branch master Already on 'master' Your branch is up to date with 'origin/master'. HEAD is now at b69075d2 updates Already up to date. Syncing net-kit branch master Already on 'master' Your branch is up to date with 'origin/master'. HEAD is now at de16b6734 updates Already up to date. Syncing text-kit branch master Already on 'master' Your branch is up to date with 'origin/master'. HEAD is now at 6c149718 updates Already up to date. Syncing science-kit branch master Already on 'master' Your branch is up to date with 'origin/master'. HEAD is now at f88a1de3 updates Already up to date. Syncing games-kit branch master Already on 'master' Your branch is up to date with 'origin/master'. HEAD is now at 21cb2b88 updates Already up to date. Syncing nokit branch master Already on 'master' Your branch is up to date with 'origin/master'. HEAD is now at 2f3b8785a0 updates Already up to date. Sync successful and kits in alignment! :) Updating /etc/portage/repos.conf... Updating profiles at /etc/portage/make.profile/parent... Updating non-funtoo repositories... Shouldn't ego be able to take care of these issues?
  3. NikosAlexandris

    Ego ImportError

    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: Funtoo's configuration tool: ego, epro, edoc. When I try to query it returns: root@carbon nik # ego query v ego ERROR: Ego encountered an unexpected error: ImportError ERROR: Full traceback written to /tmp/ego-traceback-14901.txt. The file /tmp/ego-traceback-14901.txt contains: No module named 'appi'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 100, in run_ego_module mod = loader.load_module() File "<frozen importlib._bootstrap>", line 539, in _check_name_wrapper File "<frozen importlib._bootstrap>", line 1614, in load_module File "<frozen importlib._bootstrap>", line 596, in _load_module_shim File "<frozen importlib._bootstrap>", line 1220, in load File "<frozen importlib._bootstrap>", line 1200, in _load_unlocked File "<frozen importlib._bootstrap>", line 1129, in _exec File "<frozen importlib._bootstrap>", line 1471, in exec_module File "<frozen importlib._bootstrap>", line 321, in _call_with_frames_removed File "/usr/share/ego/modules/query.ego", line 8, in <module> import appi ImportError: No module named 'appi' How do I work around this?
  4. aitikin

    ego sync failing SOLVED

    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 doing mv /var/git/meta-repo /var/git/meta-repo.bkup ego sync Syncing meta-repo fatal: Too many arguments. usage: git clone [<options>] [--] <repo> [<dir>] [truncated for readability] ERROR: Could not clone meta-repo at '/var/git/meta-repo'. Other ideas/suggestions?
  5. Oleg Vinichenko

    ego-2.6.0 released

    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
  6. 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 not remove any packages * unless *all* required dependencies have been resolved. As a * consequence of this, it often becomes necessary to run * `emerge --update --newuse --deep @world` prior to depclean. Calculating dependencies... done! >>> Calculating removal order... >>> These are the packages that would be unmerged: sys-boot/grub selected: 2.02-r1 protected: none omitted: none sys-boot/efibootmgr selected: 15 protected: none omitted: none media-libs/freetype selected: 2.8 protected: none omitted: none sys-libs/efivar selected: 35 protected: none omitted: none All selected packages: =sys-boot/efibootmgr-15 =sys-boot/grub-2.02-r1 =sys-libs/efivar-35 =media-libs/freetype-2.8 >>> 'Selected' packages are slated for removal. >>> 'Protected' and 'omitted' packages will not be removed. Packages installed: 434 Packages in world: 22 Packages in system: 81 Required packages: 430 Number to remove: 4 I have not removed any of the packages listed in the output and wanted to ask if this is expected and intended behavior. Pulling out grub seems a little bit reckless. If I remember correctly, following the Funtoo Install Guide caused grub to be pulled in as a dependency of boot-update. Perhaps the upgrade instructions for ego 2.6.0 should be expanded to cover this. In the meantime I'll just add sys-boot/grub to my world file.
  7. 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", line 87, in __call__ self.handle() File "/usr/share/ego/modules/sync.ego", line 342, in handle self.sync_meta_repo() File "/usr/share/ego/modules/sync.ego", line 192, in sync_meta_repo meta_repo_path.touch() File "/usr/lib64/python3.6/pathlib.py", line 1236, in touch fd = self._raw_open(flags, mode) File "/usr/lib64/python3.6/pathlib.py", line 1044, in _raw_open return self._accessor.open(self, flags, mode) File "/usr/lib64/python3.6/pathlib.py", line 387, in wrapped return strfunc(str(pathobj), *args) OSError: [Errno 30] Read-only file system: '/var/git/meta-repo/.touch' If I set another path for meta-repo: "meta_repo_path = /var/git/meta-repo-local" than ego sync work without issues. local meta-repo and read-only meta-repo are identical. Any chance for ego sync work on read only meta-repo?
  8. 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 /var/git/meta-repo/kits/core-kit/profiles/ !!! (You can safely ignore this message when syncing. It's harmless.) # ls -al /etc/portage/make.profile lrwxrwxrwx 1 root root 62 Aug 7 10:48 /etc/portage/make.profile -> /var/git/meta-repo/kits/core-kit/profiles/funtoo/1.0/linux-gnu "epro flavor server" prints out a huge stacktrace. "emerge --info" does the same: File "/usr/lib64/python2.7/site-packages/portage/package/ebuild/_config/LocationsManager.py", line 249, in _addProfile self._addProfile(parentPath, repositories, known_repos) File "/usr/lib64/python2.7/site-packages/portage/package/ebuild/_config/LocationsManager.py", line 249, in _addProfile self._addProfile(parentPath, repositories, known_repos) File "/usr/lib64/python2.7/site-packages/portage/package/ebuild/_config/LocationsManager.py", line 249, in _addProfile self._addProfile(parentPath, repositories, known_repos) File "/usr/lib64/python2.7/site-packages/portage/package/ebuild/_config/LocationsManager.py", line 227, in _addProfile parents = grabfile(parentsFile) File "/usr/lib64/python2.7/site-packages/portage/util/__init__.py", line 131, in grabfile mylines = grablines(myfilename, recursive, remember_source_file=True) File "/usr/lib64/python2.7/site-packages/portage/util/__init__.py", line 574, in grablines mode='r', encoding=_encodings['content'], errors='replace') as myfile: File "/usr/lib64/python2.7/codecs.py", line 303, in __init__ IncrementalDecoder.__init__(self, errors) RuntimeError: maximum recursion depth exceeded while calling a Python object So basicaly i'm stuck here and don't know how to continue. "ego sync" is working fine, so the meta-repo structure seems to be OK. Can anyone please help me to get back a working system? Thank you, Thomas
  9. 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/arch/x86-64bit/subarch/core2_64 core-kit:funtoo/1.0/linux-gnu/flavor/workstation core-kit:funtoo/1.0/linux-gnu/mix-ins/print core-kit:funtoo/1.0/linux-gnu/mix-ins/no-systemd core-kit:funtoo/1.0/linux-gnu/mix-ins/xfce core-hw-kit:funtoo/kits/python-kit/3.6-prime core-kit:funtoo/kits/python-kit/3.6-prime desktop-kit:funtoo/kits/python-kit/3.6-prime dev-kit:funtoo/kits/python-kit/3.6-prime editors-kit:funtoo/kits/python-kit/3.6-prime games-kit:funtoo/kits/python-kit/3.6-prime gnome-kit:funtoo/kits/python-kit/3.6-prime java-kit:funtoo/kits/python-kit/3.6-prime kde-kit:funtoo/kits/python-kit/3.6-prime media-kit:funtoo/kits/python-kit/3.6-prime net-kit:funtoo/kits/python-kit/3.6-prime nokit:funtoo/kits/python-kit/3.6-prime perl-kit:funtoo/kits/python-kit/3.6-prime php-kit:funtoo/kits/python-kit/3.6-prime python-kit:funtoo/kits/python-kit/3.6-prime science-kit:funtoo/kits/python-kit/3.6-prime security-kit:funtoo/kits/python-kit/3.6-prime text-kit:funtoo/kits/python-kit/3.6-prime ruby-kit:funtoo/kits/python-kit/3.6-prime haskell-kit:funtoo/kits/python-kit/3.6-prime ml-lang-kit:funtoo/kits/python-kit/3.6-prime lisp-scheme-kit:funtoo/kits/python-kit/3.6-prime xfce-kit:funtoo/kits/python-kit/3.6-prime lang-kit:funtoo/kits/python-kit/3.6-prime llvm-kit:funtoo/kits/python-kit/3.6-prime python-modules-kit:funtoo/kits/python-kit/3.6-prime xorg-kit:funtoo/kits/python-kit/3.6-prime
  10. 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"
  11. Otakku

    About new kit released.

    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.
  12. walterw

    new kits, master branch [SOLVED]

    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 also automate testing of the builds that I generate so I can ensure when I update my system, it will reliably run.
  13. 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.
  14. 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?
  15. drobbins

    ego-2.3.1 releaed

    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.
  16. 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. Best Regards, Daniel
  17. NikosAlexandris

    Failure to sync ruby-kit

    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 master -> origin/master Fetching submodule kits/games-kit From https://github.com/funtoo/games-kit 0a837932..f8224668 master -> origin/master Fetching submodule kits/net-kit From https://github.com/funtoo/net-kit 0e504bca..596dc3a4 master -> origin/master Fetching submodule kits/nokit From https://github.com/funtoo/nokit 555835154..81bc3795c master -> origin/master Fetching submodule kits/php-kit From https://github.com/funtoo/php-kit c023c17..c8d52ff master -> origin/master Fetching submodule kits/science-kit From https://github.com/funtoo/science-kit 8f33ab52..2de54760 master -> origin/master Fetching submodule kits/text-kit From https://github.com/funtoo/text-kit 28b79a6..6d4b568 master -> origin/master Updating 5699fe0..8129545 Fast-forward kits/core-kit | 2 +- kits/editors-kit | 2 +- kits/games-kit | 2 +- kits/net-kit | 2 +- kits/nokit | 2 +- kits/php-kit | 2 +- kits/science-kit | 2 +- kits/text-kit | 2 +- metadata/kit-sha1.json | 18 +++++++++--------- 9 files changed, 17 insertions(+), 17 deletions(-) Syncing core-kit branch 1.0-prime Already on '1.0-prime' Your branch is behind 'origin/1.0-prime' by 3 commits, and can be fast-forwarded. (use "git pull" to update your local branch) HEAD is now at 366dddf7 updates Updating 366dddf7..be579f3e Fast-forward app-admin/ego/Manifest | 1 + app-admin/ego/ego-2.3.0.ebuild | 67 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ metadata/md5-cache/app-admin/ego-2.3.0 | 12 ++++++++++++ profiles/package.mask/00-gentoo | 21 --------------------- profiles/package.mask/funtoo-cautionary | 2 ++ 5 files changed, 82 insertions(+), 21 deletions(-) create mode 100644 app-admin/ego/ego-2.3.0.ebuild create mode 100644 metadata/md5-cache/app-admin/ego-2.3.0 Syncing core-hw-kit branch master Already on 'master' Your branch is up-to-date with 'origin/master'. HEAD is now at adaaf60 updates Already up-to-date. Syncing security-kit branch 1.0-prime Already on '1.0-prime' Your branch is up-to-date with 'origin/1.0-prime'. HEAD is now at ff9ab7f updates Already up-to-date. Syncing xorg-kit branch 1.19-prime (non-default) Already on '1.19-prime' Your branch is up-to-date with 'origin/1.19-prime'. HEAD is now at 0f90b019 updates Already up-to-date. Syncing gnome-kit branch 3.20-prime Already on '3.20-prime' Your branch is up-to-date with 'origin/3.20-prime'. HEAD is now at e1f2ca47 updates Already up-to-date. Syncing kde-kit branch 5.10-prime Already on '5.10-prime' Your branch is up-to-date with 'origin/5.10-prime'. HEAD is now at 618949cf updates Already up-to-date. Syncing media-kit branch 1.0-prime Already on '1.0-prime' Your branch is up-to-date with 'origin/1.0-prime'. HEAD is now at 8f7d5007 updates Already up-to-date. Syncing perl-kit branch 5.24-prime Already on '5.24-prime' Your branch is up-to-date with 'origin/5.24-prime'. HEAD is now at 253b25b6 updates Already up-to-date. Syncing python-kit branch 3.4-prime Already on '3.4-prime' Your branch is up-to-date with 'origin/3.4-prime'. HEAD is now at 4fb70a17 updates Already up-to-date. Syncing php-kit branch master Already on 'master' Your branch is behind 'origin/master' by 2 commits, and can be fast-forwarded. (use "git pull" to update your local branch) HEAD is now at c023c17 updates Updating c023c17..c8d52ff Fast-forward dev-lang/php/Manifest | 9 +- dev-lang/php/php-5.6.31.ebuild | 4 +- dev-lang/php/{php-7.1.9.ebuild => php-5.6.32.ebuild} | 148 +++++++++++++++++++---------- dev-lang/php/php-7.0.23.ebuild | 4 +- dev-lang/php/{php-7.0.24.ebuild => php-7.0.25.ebuild} | 4 +- dev-lang/php/{php-7.1.10.ebuild => php-7.1.11.ebuild} | 4 +- dev-lang/php/php-7.2.0_rc3.ebuild | 734 ------------------------------------------------------------------------------------------------------------------------------------------------ dev-lang/php/{php-7.2.0_rc2.ebuild => php-7.2.0_rc5.ebuild} | 8 +- metadata/md5-cache/dev-lang/php-5.6.31 | 6 +- metadata/md5-cache/dev-lang/php-5.6.32 | 14 +++ metadata/md5-cache/dev-lang/php-7.0.23 | 6 +- metadata/md5-cache/dev-lang/{php-7.0.24 => php-7.0.25} | 6 +- metadata/md5-cache/dev-lang/{php-7.1.10 => php-7.1.11} | 6 +- metadata/md5-cache/dev-lang/php-7.1.9 | 14 --- metadata/md5-cache/dev-lang/php-7.2.0_rc2 | 14 --- metadata/md5-cache/dev-lang/{php-7.2.0_rc3 => php-7.2.0_rc5} | 6 +- 16 files changed, 145 insertions(+), 842 deletions(-) rename dev-lang/php/{php-7.1.9.ebuild => php-5.6.32.ebuild} (86%) rename dev-lang/php/{php-7.0.24.ebuild => php-7.0.25.ebuild} (99%) rename dev-lang/php/{php-7.1.10.ebuild => php-7.1.11.ebuild} (99%) delete mode 100644 dev-lang/php/php-7.2.0_rc3.ebuild rename dev-lang/php/{php-7.2.0_rc2.ebuild => php-7.2.0_rc5.ebuild} (99%) create mode 100644 metadata/md5-cache/dev-lang/php-5.6.32 rename metadata/md5-cache/dev-lang/{php-7.0.24 => php-7.0.25} (97%) rename metadata/md5-cache/dev-lang/{php-7.1.10 => php-7.1.11} (97%) delete mode 100644 metadata/md5-cache/dev-lang/php-7.1.9 delete mode 100644 metadata/md5-cache/dev-lang/php-7.2.0_rc2 rename metadata/md5-cache/dev-lang/{php-7.2.0_rc3 => php-7.2.0_rc5} (97%) Syncing java-kit branch 1.1-prime Already on '1.1-prime' Your branch is up-to-date with 'origin/1.1-prime'. HEAD is now at 3be8a29 updates Already up-to-date. Syncing ruby-kit branch 1.1-prime fatal: Could not change back to '/home/nik': Permission denied Could not clone kit 'ruby-kit' into '/var/git/meta-repo/kits/ruby-kit'. What is not ok here?
  18. 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
  19. drobbins

    ego-2.2.1 released

    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.
  20. drobbins

    ego-2.2.0 released

    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 create a kit, I may call it 1.1-prime if the goal is to make it production-quality, but the moment it is created, it is still considered 'dev' (developers only) status. Type "man ego-kit" for more information on this. It is now also possible to view a similar listing, but one that displays ALL available kits and their stability levels, by typing: # ego kit list This new release of ego also includes a host of other improvements, such as improvements to the "ego doc" MediaWiki parser. Enjoy, Daniel
  21. NikosAlexandris

    Sticky post for the switch to Kits?

    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
×