Protected garmin file toolkit not unlocking 2016.2

#Protected garmin file toolkit not unlocking 2016.2 how to
#Protected garmin file toolkit not unlocking 2016.2 upgrade

Thank you all so much for you help!Д¬heckout #grandmasboy on freenode.chat with jayP bot from the movie! That did it.I over rode PYTHON_TARGETS and set the python version to 3.3 and it worked! I didn't know that was actually set in my profile.

Or force portage to do what you want (less safe, make sure you have quickpkg or other possibilities to recover) with -nodeps You might also tells portage to not care about something with -exclude So it mean you can again instruct portage on your wish: emerge -u1 portage python:2.7 python:3.3 python-exec layman gentoolkit (if you follow the logic, yes i would had myself add dev-python/setuptools to that list) In the same way you have tell portage to handle python and python-exec, you could keep telling portage what you want.ДЇor your case, as dol-sen explains here layman and gentoolkit must be built with same python as portage. While for you it might still block the upgrade, it's not the same problem, your state are all gone. Sorry, you have no more the block problem, but slot conflict. PYTHON_TARGETS='python2_7 python3_3' emerge -av1 portage

#Protected garmin file toolkit not unlocking 2016.2 how to

But you should have some good clues on how to fix this now? Which is why I asked for the contents of /etc/portage/nf and /etc/portage/package.accept_keywords. Then to emerge ~ portage you will need to move to ~ versions of python 2.7 and 3.4 in package.accept_keywordsД«ut as I suspect you have ~amd keyworded specific packages dev-lang/python-2.7.9.r1 and dev-lang/python-3.3.5.r1 in package.accept_keywords portage will not be able to figure out how to give you the defaults until you fix these up. If don't have a specific use for python-3.3 you probably should just jump to the default which is what you get if you remove the PYTHON_TARGETS directive from /etc/portage/nf (I assume you have a directive there that is keeping you at 3.3) You also have out of tree versions of Quote:Дev-lang/python: 2.7.9-r1::gentoo, 3.3.5-r1::gentoo You have python2.7 and python3.3 installed but PYTHON_TARGETS='python2_7 python3_4' dev-lang/python-3.4.4 USE='gdbm ipv6 ncurses readline ssl threads xml -build -examples -hardened -libressl -sqlite -tk -wininst' * Use eselect news read to view new items. * IMPORTANT: 23 news items need reading for repository 'gentoo'. Localhost filter # emerge -u1 portage python:2.7 python:3.3 python-exec Thanks.still having the block issue with emerge -u1 portage python:2.7 python:3.3 python-exec: This way you will hint portage that all should be handle, and the blocker should be gone.

#Protected garmin file toolkit not unlocking 2016.2 upgrade

You need to upgrade your python to 2.7 and 3.3 prior having python-exec build.Д®merge portage: you tell portage you want portageД«ut portage is complaining about python version and python-exec, you can generally hint portage on howto handle thisД®merge -u1 portage python:2.7 python:3.3 python-exec I suspect I know the issue here, but I'm not confident I could advise a solution on the basis of the emerge output alone. Checkout #grandmasboy on freenode.chat with jayP bot from the movie!Д¬an you post the contents of your /etc/portage/nf, /etc/portage/package.accept_keywords and output of Code: app-eselect/eselect-python-20160222::gentoo 48 KiB dev-lang/python-3.4.4:3.4/3.4m::gentoo USE='gdbm ipv6 ncurses readline ssl threads xml -build -examples -hardened -libressl -sqlite -tk -wininst' 13,984 KiB sys-apps/install-xattr-0.5::gentoo 16 KiB

These are the packages that would be merged, in order: what is the best way to handle thsse Python blocks? I'm scared if I remove them I will break portage. Posted: Mon 3:18 am Post subject: Portage upgrade and python blocks Gentoo Forums Forum Index Portage & Programming Gentoo Forums :: View topic - Portage upgrade and python blocks