[AssertionError: setcpv recursion detected]

oh well didn't see your last post you made 3 hours ago

[AssertionError: setcpv recursion detected]

thats odd, my portage is 2.3.12 does not even show 2.3.11

looks like your repo is not syncing correctly

 file a bug report on your original post error.

give your info like,

epro show

emerge --info 

maybe make.conf ect..

~$ ego query v portage
 sys-apps/portage| slot|               repo
-----------------+-----+-------------------
            2.3.8|    0| core-kit/1.0-prime
         2.3.8-r4|     | core-kit/1.0-prime
         2.3.8-r5|     | core-kit/1.0-prime
         2.3.8-r6|     | core-kit/1.0-prime
         2.3.8-r7|     | core-kit/1.0-prime
         2.3.8-r8|     | core-kit/1.0-prime
         * 2.3.12|     | core-kit/1.0-prime

regards,

[AssertionError: setcpv recursion detected]

yes you have changed to  meta-repo  ego is the way now to sync  kits by giving command "ego sync"

what kind of error do you get when trying to update ego? may give a clue about what has gone wrong.

from the looks of the error you posted your version of portage is possibly dated, just a guess here.

[AssertionError: setcpv recursion detected]

there have been alot of changes to ego and friends over the last month

maybe try to update ego

emerge  -1 ego

see if that helps

[LLVM_TARGETS for intel?]

Thanks Oleg!,

I stand corrected.

dave

[LLVM_TARGETS for intel?]

I only asked this because I updated gcc  on my dell notebook and I new I was about to recompile everything.

 so the only answer I could find is from  "so"  ,  mostly talks about clang , which I have no idea IF i even need this stuff on my system.

x86-64 - 64-bit X86: EM64T and AMD64

for Intel cpu.

[LLVM_TARGETS for intel?]

Is it ok to not set this in make.conf ? or in other words do we need to set llvm targets?

thanks.

[Killer NIC e2200 not getting DHCP]

ok according to the gentoo wiki having both or several dhcp packages will cause problems , well you could try to kick networkmanager or dhcpcd and see if one by itself will work.

https://wiki.gentoo.org/wiki/Network_manager

[Killer NIC e2200 not getting DHCP]

just to add I myself do a static ip its a desktop but dhcpcd is also default runlevel as is netif.eth0

~$ cat /etc/conf.d/netif.eth0
template="interface"
ipaddr="192.168.0.101/24"
gateway="192.168.0.1"
nameservers="192.168.0.1"
domain=""

but if your on a notebook the dhcpcd above should do.

[Killer NIC e2200 not getting DHCP]

if your using network-manager there should be no configuration from my understanding the docs.

or for dhcpcd you do

# cd /etc/init.d
# ln -s netif.tmpl net.eth0
# rc-update add net.eth0 default
# echo template=dhcpcd > /etc/conf.d/net.eth0
# rc

[Killer NIC e2200 not getting DHCP]

ok probably configuration problem

contents of '/etc/conf.d/net.eth0' ?

or mabe is /etc/conf.d/netif.eth0

[Killer NIC e2200 not getting DHCP]

how about 'ifconfig -a'?

contents of '/etc/conf.d/net.eth0' would also be helpful.

possible clue is

ipv6_addaddr1: Permission denied

 is your router giving ipv6 or ipv4?

[Killer NIC e2200 not getting DHCP]

curious  try 'lsmod | grep alx'

I think module mdio should also load with alx

 

[Change to kits and python confusion]

2 hours ago, pytony said:

`epro update` updates the contents of the file `/etc/portage/make.profile/parent`. This file contains profiles that determine default useflags, masks, make.conf, ... These profiles depend on the python-kit branch you use and profiles you set with epro.

`epro update` is indeed missing from documentation. You can file an issue on Jira about it.

Hey thanks for all the info, and I did see something about that on bugs. but the only other place I saw it documented was my reference above.

 

['equery list --portage-tree' with kits]

I usualy use eix. but now there is

ego query versions <package>

[Change to kits and python confusion]

oh yeah , forgot about this post,

from what I have found from digging around some is still unclear.

Unofficially,

its  used after making changes to /etc/ego.conf

Example

say you wanted to use to python3_6 you put

python-kit = 3.6-prime

into ego.conf

run epro update to make the change permanent

ego sync would make it available to merge

I'm not sure how to go about rebuilding against python3_6 at all.

maybe there will be some news about it at some point.

[python woes]

mauricev  a change has appeared on this page mabe try this I think its slightly different then what you were trying?

 

https://www.funtoo.org/index.php?title=News:Python_Multiplexing(And_another_Ego_update)&oldid=19639

 

hth,

 

dave

[python woes]

Hi, I think it qualifies as a bug..

 

posting the result of emerge --info and contents of make.conf would go along way in seeing part of whats happening, but

 

posting to bugs.funtoo.org should get more responses.

 

just found this : http://www.funtoo.org/index.php?title=News:Python_Multiplexing(And_another_Ego_update)&diff=19639&oldid=19021

 

but I think you have already tried this?

 

dave

[eselect python doesn't seem to be working?]

I saw in a news item a while ago that eselect python would go away..

No idea if it did butl I think ego is taking care of it since change to kits.

an example

editing of /etc/ego.conf
setting python-kit = 3.6-prime
running epro update.

 

info is from https://bugs.funtoo.org/projects/FL/issues/FL-4270?filter=allissues

 

I know that bug was concerning lv2 but shows how to correctly switch python versions with kits. IMO.

 

Please correct me if i'm wrong!

 

dave

[python woes]

nrc, you make a valid point I never considered the --nodeps may work as well,. thanks for that!

 

look at your eix result and then look at mine.. 

 

I don't know why they would be different but it might be a problem

 

edit: I looked and perhaps that is perfectly acceptable, .

[I] app-admin/ego
     Available versions:  2.0.9^m **2.0.10^m **2.0.12^m {zsh-completion PYTHON_SINGLE_TARGET="python3_4 python3_5 python3_6" PYTHON_TARGETS="python3_4 python3_5 python3_6"}
     Installed versions:  2.0.9^m(08:20:57 PM 09/13/2017)(-zsh-completion PYTHON_SINGLE_TARGET="python3_4 -python3_5 -python3_6" PYTHON_TARGETS="python3_4 -python3_5 -python3_6")
     Homepage:            http://www.funtoo.org/Package:Ego
     Description:         Funtoo's configuration tool: ego, epro, edoc.

the problem is your python use flags and profile got disconnected from portage with the meta-repo change.

add dev-python/setuptools dev-python/appi app-admin/ego to portage.use with a python target and a python single target.

How you write them PYTHON_TARGETS_PYTHON3_4 or PYTHON_TARGET="python3_4" ? may or may no matter.

I would recommend python3_4 as a single and 3_4 2_7 as python target.

 

then run emerge -1 dev-python/setuptools dev-python/appi app-admin/ego

[python woes]

would you mind posting your make.conf?

[python woes]

when did you last update your tree?

 

# cd /var/git/meta-repo
# git pull
# git submodule init
# git submodule update
# emerge -1 ego

 

I had much the same problem but it didn't take long to workaround.

 

you have eix?

eix app-admin/ego

[python woes]

what do you get by doing:

 

 eselect python list

[python woes]

ah yea, that all looks very familiar to me, except for the profile part.

 

there was a news item that said to update ego back in august that i missed , I think it was 1.1.3-r?

that version is no longer in the tree.

 

I think this is how I got past the problem putting in make.conf

PYTHON_SINGLE_TARGET="python3_4"
PYTHON_TARGETS="python2_7 python3_4"
 

thats assuming you have python3_4 still.

then try emerge ego again.

[Change to kits and python confusion]

I was away from pc end of august so I miss the 8-25 news about changing kits and ego bumping

and found workaround with python targets in make.conf which I have seen it as not a good solution.

 

I have seen this epro update command several times but there is nothing in the docs I found about it.

could someone please explain this command?

 

thanks

 

dave