Jump to content
funtoo forums

Search the Community

Showing results for tags 'kits'.



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


web


First Name


Last Name


Location


Interests

Found 17 results

  1. 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?
  2. Hi all, I wanted to open a discussion about collecting some anonymous usage data about funtoo kits and maybe some more metrics from your computers. What are your thoughts about it? This is what for example Nextcloud is using and collecting: Actual data sent: { "id": "oc9f8tble2uv", "items": [ [ "server", "version", "12.0.3.3" ], [ "php", "version", "7.1.10" ], [ "php", "memory_limit", 536870912 ], [ "php", "max_execution_time", 0 ], [ "php", "upload_max_filesize", 10737418240 ], [ "database", "type", "pgsql" ], [ "database", "version", "PostgreSQL 9.6.4 64-bit" ], [ "database", "size", 82090520 ], [ "apps", "audioplayer", "disabled" ], ... You get the idea. We can discuss what types of metrics could make sense to collect. Let me know what you thing about it.
  3. Let me preface this post by saying I hope it will be constructive. It's not my intention to simply complain or vent. I wanted to share my experience updating one of my funtoo systems the past two days, because I feel that kits (so far) may not be living up to their promise. I had hoped they would smooth over some of the headaches of system upgrades. My upgrade process went something like this: Blockers where USE=qt4 had to be added to several packages, successively. That is... emerge @world; long wait; portage reports package needs USE=qt4; add USE flag; emerge @world; long wait; portage reports package needs USE=qt4; add USE flag; emerge @world; long wait; portage reports package needs USE=qt4; and so on. Blocker related to libreoffice. I had earlier keyworded libreoffice for stable only, as I really don't need the latest and it's a beast to build. Well, at this time there isn't a single stable ebuild in the tree. Oddly, there is still a stable ebuild for libreoffice-l10n. Anyway, I had to remove the stable keyword. To resolve some other blockers, I ended up using 'emerge -C' on 5 packages (e.g., kget and media-sound/picard). I kept a list of these so I could re-merge them at the end. I removed the 'legacy-systray' USE flag from plasma-desktop to resolve some other blockers. About this time, I was finally able to get it to start installing some updates. I'm getting odd build failures for virtualbox-modules, which I ignore for now and use '--keep-going' (will come back to this). Encountered a build failure in package pambase. With research, found an issue in the tracker that was fixed yesterday morning, so needed to 'ego sync' mid-upgrade. Now, it's 'emerge @preserved-rebuild' time, but it's blocked by a conflict with package doomsday. Use 'emerge -C doomsday' to resolve. I think it was here that I dealt with the app-emulation/wine to virtual/wine change. Not terrible, though I was a bit confused why I seem to need wine-vanilla if all I want is wine-staging. Perhaps I could if I emerge 'app-emulation/wine-staging' directly instead of going through 'virtual/wine'? I didn't want to stop the upgrade at this time to figure it out. Time to resolve issue with virtualbox-modules. It's giving multiple complaints that it "can't find Makefile" and "can't find .config file", and that I need to make sure that '/usr/src/linux' points to a full kernel source tree. I check, there is nothing wrong with the symlink, it points to the folder for the current running kernel, the folder contains a Makefile and .config file, and the folder still contains sources. The only possible problem I can figure is the ebuild for this kernel is no longer in the portage tree. So, I stop to upgrade the kernel, and the problem goes away. Now it's time to re-merge the packages I removed earlier, one of which is quodlibet. Only, portage complains it can't install the latest quodlibet because of some funky python issue with package dev-python/faulthandler I don't understand. I find no mention of this in JIRA or forums, so I just let it install the old version. I've just now discovered that portage is no longer picking up my local overlay. I'll need to research that, too. It's certainly wasn't the most painful gentoo/funtoo upgrade I've ever been through, but I can't really say it was any easier than typical. Especially considering this was a shorter upgrade cycle than usual for me (only about a month), and I keep customizations on this system to a minimum. Anyway, as I said at the outset, I wanted to share my experience in the hopes it is constructive. Cheers!
  4. Hi, everyone! We are pleased to announce that media-kit 1.1-prime branch is set as default. After tree update you will notice a bunch of updates to media-related ebuilds.
  5. Can /usr/portage be deleted now that /var/git/meta-repo stores all the ebuild info?
  6. 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.
  7. 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.
  8. 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?
  9. Hey All, If you have a Funtoo container and would like to upgrade to kits, please contact me. I can reload your container so you can start with a 'fresh' system that is set up to work with kits from the beginning. The actual re-image process takes about 5 minutes to complete. It does require that you back up your important data, and once reloaded, your container will need your favorite apps emerged again. Regards, Daniel
  10. hello again, i've the following set into my ego.conf: xorg-kit = 1.19-prime media-kit = 1.1-prime kde-kit = master however on today sync i've got this message: "Kit kde-kit branch master specified in ego.conf is not currently active; using default kit instead." so why can i not choose kde-kit's master branch anymore in ego.conf? i've forced the master branch checkout by adding: @git -C /home/meta-repo/kits/kde-kit checkout origin/master || true into eix-sync.conf, however i wonder why these kind of hacks are necessary... thank you
  11. 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
  12. Hey everyone, I've just added a new kit called lang-kit, which is a kit for all programming languages that do not have their own kit. This includes mono, fsharp, node.js, tcl-tk, lua, go, erlang and associated categories, plus all of dev-lang that doesn't end up in its own kit. Lang-kit should be appearing within the next hour after your next ego sync. This kit was created to address a nodejs upgrade issue that is causing some issues in the tree and will allow us to lock-in node.js which is getting frequently updated by gentoo upstream. Regards, Daniel
  13. Hi all, A multitude of new kits are coming your way. I'll give you a list of what they are and share other kit-related updates with you. The new kits you'll be seeing soon are: ruby-kit, haskell-kit, ml-lang-kit, lisp-scheme-kit, and xfce-kit. With the exception of xfce-kit, these kits are all essentially sub-kits of dev-kit (and now have their own kit, just to try to pare down dev-kit a bit.) xfce-kit is for the XFCE 4.12 desktop environment. In addition, we have snapshotted/frozen the following kits: *java-kit*, ruby-kit, haskell-kit, ml-lang-kit, lisp-scheme-kit, *dev-kit*, xfce-kit and *desktop-kit*. Note that the kits in red are ones that previously following gentoo-current, and are now snapshotted as of today (Oct 22). The other kits listed are the new kits. With this wave of new kits, I am pushing forward the kit paradigm. With additional snapshotting of previously 'current' kits, I am putting funtoo's developer focus on getting the new 1.1-prime core-kit, media-kit and friends truly ready for production. The goal is to shift major updates to that they come via kit upgrades rather than a trickle of new package updates. What should you expect over the rest of the year? Expect further stabilization of our now-snapshotted kits. Also, when PHP 7.2.0 is released, expect a php-kit that will be snapshotted at 7.2-prime rather than following current as it does now. You should also expect to see a new generation of kits made available so you can select more recent packages. Also on the radar are automated features to help switch kits cleanly -- think of these as things like perl-cleaner and friends but that get automatically triggered when you switch kits to ensure a smooth transition. And yes, you will likely see a few more kits added to the mix, along with new ego features. With these new kits, the kit paradigm has been further advanced and will continue to advance. Along the way, you may feel that Funtoo Linux updates are getting 'stuck' or not going as quickly as you like, due to kits being frozen. If this impacts you, please provide us with feedback so we are aware of what things you need updated and why -- and understand that the pause in version bumps is more of a temporary phenomenon rather than a permanent reality. The updates will come -- in the form of kit bumps! The adjustment of our dev process will happen, and soon will reap rewards by offering stability as well as the latest ebuilds for you to choose from. Please feel free to share your questions and concerns on this thread. Best Regards, Daniel
  14. skunk

    kits logic

    hello devs (oleg) :) i wonder what are the rules behind this new kit organization... do packages from the master branch eventually make into a prime branch or are prime branches virtually immutable? if the former, after lying into the the master branch for some time (like gentoo's stable/unstable)? how long? any other criterion instead? if the latter, are "stable users" supposed to jump from prime-n to prime-n+1 branches at their discretion? for example i'm on the default 5.10-prime kde-kit's branch and i see that kde-plasma-5.11.0, kde-frameworks-5.39 and kde-apps-17.08.2 were added to the master branch. i expect at least kde-apps-17.08.2 to make into the 5.10-prime branch since it's a bug fix release, while kde-plasma-5.11.0 to be sometimes added to a new default 5.11-prime branch since it's a major release, not sure about frameworks-5.39 but i consider it pretty safe to include it into 5.10-prime after reaching master for some time... so just curious to know how this new kit organization method works and what's its internal rules :) thank you
  15. skunk

    eix and kits

    hello funtooers, i've managed to upgrade my box from kde4/stable/ports-2012 to plasma5/current/meta-repo, however i'm really missing the eix tool to search for packages and querying installed ones... is there a way to make eix work with kits? thank you!
  16. 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...