jhan

Where do you get the idea from that the CFLAGS are dropped? When I look at a build.log file I still see all the CFLAGS I have set.

Are there currently no updates delivered? For a few days I haven't got any updates for my system, not even vim. The only unusual I see in the output is the mention of a "detached head" for the core kit (see attached file). I already tried to drop the local git directory and reload it but no difference. egosync.txt

Good question. You could always report it as a bug at bugs.funtoo.org

I think you either need to use the use flag "-asn1" or install dev-libs/libtasn1.

The question is, which config files are we talking about? Are those config files then different for each container or could you provide them for the containers from a "master config" as well? If you can't do that, you are pratically looking for another switch for ego-sync, something like "--config-only", or? Just to understand the way you are using the meta-repo. You use ego-sync to update the config files in your containers but what do you use the updated information for?

In that case you probably don't need the "ego sync" for the containers at all. Just run "ego sync" on a writable system once and share this meta-repo data with the containers. "ego sync" would get a current meta-repo and in the containers you would only use something like "emerge --update" and not "ego sync", as that has already been done, and is available through the shared directories.

The first question that pops into my mind is: What are you trying to accomplish here? ego sync updates the local repo with the changes of the global one. That will not work on a read-only file system. So, what is your reasoning for keeping the meta-repo read-only? And what do you expect to happen when you sync it?

So called ivybridge processors come in different shapes and sizes. And your cpu does not seem to support aes or avx. Thus the stage3 you used is not the correct one, as it uses avx: https://www.funtoo.org/Intel64-ivybridge I would start with a generic stage3 first: https://www.funtoo.org/Generic_64 and then use the tool cpuid2cpuflags to find the supported cpu flags and then recompile the system with the supported cpu flags set.

I think that this could be because LINGUAS support is slowly replaced by L10N: https://www.gentoo.org/support/news-items/2016-06-23-l10n-use_expand.html I think there was a similar problem a while ago with KDE. But it seems that some packages still haven't switched over.

Hmm...if I understand all that correctly, it sounds to me that you are complicating the matter. I would just write myself a simple script which would do the following: - Do a pre-install snapshot - emerge everything (or do other damaging stuff) - Do a post-install snapshot I see no need to involve portage in it, other than it is intended to do already. But I might not be understand what you are trying to accomplish here. In that case please elaborate.

I think you are mistaken by setting PORTDIR to "/var/git/meta-repo/kits/core-kit/". As you output shows, eix-update is only updating core-kit. And eix is part of "nokit". So it is clear that eix could not be found. Besides, the problem is, that you need to set PORTDIR in the first place. As far as I know this variable could generally be used when you work with overlays but is not needed for the standard tree. So, do you work with overlays and might have changed something that could influence eix?

OK, a few things to check here: - Why do you have meta_repo_path in ego.conf? Any special reason? I don't have that line and eix-update works for me - What does /etc/eixrc/00-eixrc look like?

It could be a remnant of an earlier "build" or be pulled in by some other package. This output shows that xorg-drivers should not the responsible for installing synaptics but maybe another package. For that use the command @Otakku provided. And for synaptics being a remnant you could use the command 'emerge -pv --depclean'. If synaptics shows up in the output, that would be a good indication for that.

I think that the use of meta packages in funtoo is more elegant than that. Have a look at the output of 'emerge -s meta' and the ebuilds for those packages.

Does that mean that you found the reason? If yes, what was the problem?