| Summary: | adding python3_5 to PYTHON_TARGETS breaks update | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | John (EBo) David <ebo> |
| Component: | Current packages | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
| Status: | RESOLVED TEST-REQUEST | ||
| Severity: | normal | ||
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: | required emerge --info | ||
Simply adding python3_5 to PYTHON_TARGETS is not enough to enable Python-3.5 support on a stable system. Please refer https://wiki.gentoo.org/wiki/Project:Python/PYTHON_TARGETS#Unmasking_non-stable_implementation_on_a_stable_system If you still have this problem after following all the steps described on wiki, please reopen the bug. This was clearly my fault. I had read something somewhere that gave me the impression that Python 3.5 was now stable. Fortunately this bug report should help a lot of other folks who are having the same problem. Do you still want a test-request? If so, what test(s) would you liked run? After rereading your comment I see that you you wanted me to try unmasking Python-3.5 and test. This exposed a circular dependency that will break my current work toolchain. I will have to work on this later in the week. (In reply to John (EBo) David from comment #2) > This was clearly my fault. I had read something somewhere that gave me the > impression that Python 3.5 was now stable. > > Fortunately this bug report should help a lot of other folks who are having > the same problem. > > Do you still want a test-request? If so, what test(s) would you liked run? If as you say it was just a misunderstanding and you don't really want to experiment with unstable python-3.5, then no further testing is needed. Thanks. See also https://bugs.gentoo.org/show_bug.cgi?id=576742 (In reply to John (EBo) David from comment #3) > After rereading your comment I see that you you wanted me to try unmasking > Python-3.5 and test. This exposed a circular dependency that will break my > current work toolchain. I will have to work on this later in the week. I was merely showing you the right way to unlock python-3.5 on a stable system. Whether you actually want it or not is up to you. If you do, note that you'll also need to install unstable versions of some packages as python-3.5 support isn't available tree-wide in stable ebuilds atm. Would it be helpful to have someone test it? If so I will go through the hassle. If not generally helpful then it would probably be better to wait. (In reply to John (EBo) David from comment #6) > Would it be helpful to have someone test it? If so I will go through the > hassle. If not generally helpful then it would probably be better to wait. All packages mentioned in the OP (dev-python/six dev-python/traitlets dev-python/notebook) have python-3.5 support in their latest ebuilds. Your problem most likely originated from the incomplete python-3.5 setup. Thus, extra testing isn't necesasry unless you really want to. |
Created attachment 452520 [details] required emerge --info After a recent major update I got the following error: ================ emerge: there are no ebuilds to satisfy "dev-python/six[python_targets_python2_7(-)?,python_targets_python3_4(-)?,python_targets_python3_5(-)?,-python_single_target_python2_7(-),-python_single_target_python3_4(-),-python_single_target_python3_5(-)]". (dependency required by "dev-python/traitlets-4.1.0::gentoo" [ebuild]) (dependency required by "dev-python/notebook-4.1.0::gentoo" [ebuild]) (dependency required by "@selected" [set]) (dependency required by "@world" [argument]) ================ I found similar issues across the web, but finally stumbled onto the solution of removing python3_5 from PYTHON_TARGETS. I am posting this as a bug for not other reason that if python3_5 is not supported, the error message should not imply that none of the python versions are supported. Steps to Replicate: Add python3_5 to PYTHON_TARGETS and tun "emerge -uDNp world" Workaround (that worked for me): Remove python3_5 from PYTHON_TARGETS