drobbins

Well meta-repo shouldn't have any branch but master. Why not just mv /var/git/meta-repo /var/git/meta-repo.bak and do an "ego sync" again? It should give you a fresh clone of everything.

What version of ego are you running?

Try using 'monkeymonkey' to log in to the bug tracker. For some reason, the code in the forums is allowing you to sign in with your full name, but really you should have used your username. I can sync the accounts if you are ok being 'monkeymonkey' in both places.

Note that while meta-repo has submodules for backwards-compatibility purposes, they are not officially used anymore, and new versions of ego will manage the syncing of kits directly. They can be useful in a pinch and there is no harm in using 'git submodule init/update' in a rescue situation.

Are you still having the issue? I'm wondering if it was an intermittent bug triggered by the addition of lang-kit.

Note that the lang-kit is based on a snapshot of Gentoo from about 4 days ago. Thus, you may see some minor downgrades of some packages if you have updated your system in the last 3-4 days. This is normal and shouldn't cause issues.

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

I whitelisted you, so in about 5 minutes you should be able to post what you were posting.

Move over to prime versions.

I've stopped updating some master branches in anticipation of us being more aggressive in delivering prime branches that are updated, and it does take some time to generate each branch and I wanted to optimize our tree update process.

It is set in /etc/portage/make.profile/parent.

I think the answer will vary depending on the person, but I can tell you about how I set up my workstation (laptop, Thinkpad W541). Generally, I want to set things up and have a stable, productive system since I need to be able to potentially leave my home office at a moment's notice and go somewhere... and my laptop needs to work. So I use the standard kits along with gnome-3.20, and now I have xorg 1.19-prime and 3.6-prime of python-kit running. I use debian-sources because it just plan works and I have no time to play with kernels (or need to). I might reinstall every 3-6 months, just to test the installation process, but this is generally not necessary unless you really *want* to. The apps I use the most are google chrome, hangouts, JetBrains pycharm (Java IDE), git. I have cups set up so I can print. I have a small set of python modules installed from packages to support my development work.

The reason is because we stopped updating master for kde-kit, and ego knows that it's not going to get any updates. We may add it back in the future after a server upgrade, but I needed to cut back on the time required to generate all the kits for now.

Yes, in theory it could be added and would probably be a good idea if it did this. Please open a bug for this on the bug tracker and I'll add it.

Also, in addition, I'm no longer updating master on the following kits: core-kit, security-kit, xorg-kit, gnome-kit, kde-kit, media-kit, perl-kit, python-kit. I made this change to reduce the clock time required to update our kits.

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

Should now be fixed (for real). Let me know if any problems creep back.

I may need to regenerate the cache on all those wiki pages to update them.

That could potentially work, but the safest bet is a reinstall, and it may end up being less painful. It depends how much you are willing to drudge through rebuilds on an existing system.

The stage3 build download links should now be back :)

Let me just add that the wiki is the next thing on the list to be upgraded or replaced...

Ah, this was due to our migration to SSL and a new build container. I am working on restoring the list. I will post here when it's complete.

I already have a bug open and waiting for me to add the functionality to specify a kit from the command-line rather than having to edit the config file, so that will be appearing in ego shortly :)

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.

Upgrade to ego-2.2.1, and you should now have: # ego kit show # ego kit list You should also be able to do a "man ego.conf" and learn about how to set the branch of the kits you want to use.