Oleg Vinichenko
-
Posts
619 -
Joined
-
Last visited
-
Days Won
53
Content Type
Profiles
Forums
Blogs
Posts posted by Oleg Vinichenko
-
-
it looks it trying to start consolekit, while it already started.
please, when you are not in X (and better after reboot) paste output of ls -l /etc/runlevels/*/*
-
i havent seen such behavior. But will look in a fresh test.
-
ego does not switch to python-3.6 automatically as this branch is not default one. You have a choice to switch with ego.conf, then by ego sync you will get the branch cloned.
-
this looks good apart from some permission diffs.
try mv /var/git/meta-repo /var/git/meta-repo.old
and then
ego sync
this will give you a pristine fresh copy of meta-repo.
-
show output of ls -dl /var/git/meta-repo/*/*
-
ego sync does clean and reset steps, so you don't need to make them prior to 'ego sync'. or is there a reason why you making this before syncing meta-repo?
-
the fix to this is same as in post #2
are you changing the files manually in meta-repo?
-
weird.
i cannot reproduce ego nuking overlays.
i use /etc/portage/repos.conf/oleg as my local overlay and ego sync doesnt remove it, ego sync doesn't remove if i use oleg.conf too. Maybe something unrevealed. Can you show whats in /etc/portage by:
ls -dl /etc/portage/*/*
-
yes
you can save the distfiles and pkgs (binary) if its a problem, otherwise /usr/portage can be zapped
-
it is not deprecated, latest version 2.8.4 but the page not updated that's correct.
-
ext4 is also a module in debian kernel. the fix to it would loading the keyboard/usb modules before the luks and before mounting the rootfs. Currently genkernel does not do this. Alternatively those can be compiled in and not modules.
-
this is not intuitive to users, the time you can remove the uses can be the time those uses are no longer present in ebuilds or you don't need them. the first case can be determined when portage will give you a following message during emerge -auDN
app-foo/bar (-use%), that means this use is no longer present (removed)
personally i trying to avoid using package.use too much and rely on what is enabled by default in profiles.
-
this is fixed in ego-2.3.0 9 (testing ebuild). but to workaround before you should do cd /tmp and ego sync
or cd /var/tmp and ego sync
-
i think it could be good default to have apache compiled with threads. i cannot tell about downsides so far, unless there are ebuilds that do not want apache[threads]. need research
-
There are no specific LLVM_TARGETS for the Intel, take a look into brief News i made some time back, when llvm_targets introduced into Funtoo.
-
portage asks to enable threads USE
-
ok, i will add 2.2 version too, then
-
-
ah, i really stuck with xorg-server mask in my head. the xorg-server mask is fixed but xorg-drivers mask is something added after that and it's not overridden yet.
-
-
the exact gentoo mask is overridden, and i getting no this mask message anywhere on boxes. can you paste full emerge output where this message occurs.
-
show output of grep -r xorg-server /etc/portage
-
-
what dhcp client you use?
instructions for switching to kits have changed
in Portage Help
Posted
you shouldn't change anything about it unless you are using custom overlays or layman or planning to use them in future the way old instruction was results in /etc/portage/repos.conf directory to be a link to /var/git/meta-repo, thats then makes a custom overlays inside /var/git/meta-repo, which is not the good place. new instruction makes a distinct repos.conf configuration, the one to point to portage tree (meta-repo), rest can be any custom overlay. i believe better solution to it now added into unreleased version of ego.