| View previous topic :: View next topic |
| Author |
Message |
Pindrop
Apprentice
Joined: 09 Jul 2002
Posts: 165
Location: Virginia, USA
|
 Posted: Sat Jan 04, 2014 9:38 pm Post subject: python sandbox portage oh my |
 |
|
what the heck happened? who is responsible for this!  i cant update portage because it requires sandbox but is hard blocked by python...
| Code: | # emerge -up portage
These are the packages that would be merged, in order:
Calculating dependencies... done!
[ebuild NS ] dev-lang/python-3.3.2-r2 [2.7.3-r3, 3.2.3-r2] USE="gdbm ipv6 ncurses readline ssl threads xml -build -doc -examples -hardened -sqlite -tk -wininst"
[ebuild U ] sys-apps/portage-2.2.7 [2.2.1] PYTHON_TARGETS="python3_3* -python3_2*"
[blocks B ] <sys-apps/sandbox-2.6-r1 ("<sys-apps/sandbox-2.6-r1" is hard blocking dev-lang/python-3.3.2-r2)
* Error: The above package list contains packages which cannot be
* installed at the same time on the same system.
(sys-apps/sandbox-2.5::gentoo, installed) pulled in by
>=sys-apps/sandbox-2.2 required by (sys-apps/portage-2.2.7::gentoo, ebuild scheduled for merge)
(dev-lang/python-3.3.2-r2::gentoo, ebuild scheduled for merge) pulled in by
>=dev-lang/python-2.7 required by (sys-apps/portage-2.2.7::gentoo, ebuild scheduled for merge)
dev-lang/python required by (app-admin/python-updater-0.10::gentoo, installed)
dev-lang/python[xml] required by (app-portage/gentoolkit-0.3.0.7::gentoo, installed)
dev-lang/python:3.3 required by (sys-apps/portage-2.2.7::gentoo, ebuild scheduled for merge)
>=dev-lang/python-2.7[ssl] required by (sys-apps/portage-2.2.7::gentoo, ebuild scheduled for merge)
>=dev-lang/python-2.6[xml] required by (app-portage/gentoolkit-0.3.0.7::gentoo, installed)
dev-lang/python required by (app-portage/gentoolkit-0.3.0.7::gentoo, installed)
For more information about Blocked Packages, please refer to the following
section of the Gentoo Linux x86 Handbook (architecture is irrelevant):
http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?full=1#blocked |
|
|
| Back to top |
|
 |
Hu
Administrator
Joined: 06 Mar 2007
Posts: 21687
|
| Posted: Sat Jan 04, 2014 9:53 pm Post subject: |
|
|
| Portage requires the versions of Python specified in PYTHON_TARGETS. You changed PYTHON_TARGETS to request Python 3.3, so now you need Python 3.3 installed before you can install any other Python-based programs, of which Portage is one. Fix your PYTHON_TARGETS variable and try again. |
|
| Back to top |
|
|
Pindrop
Apprentice
Joined: 09 Jul 2002
Posts: 165
Location: Virginia, USA
|
| Posted: Sun Jan 05, 2014 5:57 pm Post subject: |
|
|
| Hu wrote: | | You changed PYTHON_TARGETS to request Python 3.3, so now you need Python 3.3 installed before you can install any other Python-based programs, of which Portage is one. Fix your PYTHON_TARGETS variable and try again. |
I did no such thing. Eselect python list only provides me with two options, python 2.7 and 3.2, and the latter is selected. How does one "fix" PYTHON_TARGETS? |
|
| Back to top |
|
|
VoidMage
Watchman
Joined: 14 Oct 2006
Posts: 6196
|
| Posted: Sun Jan 05, 2014 7:20 pm Post subject: |
|
|
PYTHON_TARGETS default was changed once python 3.3 was stabilized.
The obvious question is "what happens with 'emerge -1pv portage sandbox' ?". |
|
| Back to top |
|
|
Pistos
Apprentice
Joined: 29 Jul 2003
Posts: 175
Location: Canada
|
| Posted: Sun Jan 05, 2014 7:29 pm Post subject: |
|
|
| When I updated sandbox alone, I was able to move on. |
|
| Back to top |
|
|
wrc1944
Advocate
Joined: 15 Aug 2002
Posts: 3435
Location: Gainesville, Florida
|
| Posted: Mon Mar 24, 2014 7:38 pm Post subject: |
|
|
VoidMage wrote:
| Quote: | | PYTHON_TARGETS default was changed once python 3.3 was stabilized. |
I'm having problems with emerge, portage-2.2.9-r1, and python on ~Arch systems. See thread for details: https://forums.gentoo.org/viewtopic-t-987132.html
I have been selecting python-2.7 for years, but am now wondering if i need to really move on to 3.3, and then try the new 2.2.9 portage again. This the first time in over 10 years running ~Arch I can recall that a portage update broke emerge. My systems are all current ~Arch, depcleaned and revdep-rebuilt, run normally, only with portage-2.2.9 an't emerge anything- reverting to 2.2.8-r1 works perfectly, as usual.
Anyone know of any problems if i simply use eselect python to go to 3.3, and then run python-updater?
_________________
Main box- AsRock x370 Gaming K4
Ryzen 7 3700x, 3.6GHz, 16GB GSkill Flare DDR4 3200mhz
Samsung SATA 1000GB, Radeon HD R7 350 2GB DDR5
OpenRC Gentoo ~amd64 plasma, glibc-2.36-r7, gcc-13.2.1_p20230304
kernel-6.8.4 USE=experimental python3_11 |
|
| Back to top |
|
|
TomWij
Retired Dev
Joined: 04 Jul 2012
Posts: 1553
|
| Posted: Tue Mar 25, 2014 8:21 pm Post subject: Re: python sandbox portage oh my |
|
|
| Pindrop wrote: | | [blocks B ] <sys-apps/sandbox-2.6-r1 ("<sys-apps/sandbox-2.6-r1" is hard blocking dev-lang/python-3.3.2-r2) |
This line means you either need to update sandbox (`emerge -1 '>=sys-apps/sandbox-2.6-r1'`) or find a version of dev-lang/python that doesn't have this blocker (`grep -r sandbox /usr/portage/dev-lang/python/` lists those that have the blocker, `eix dev-lang/python` lists all versions; it seems as only newer versions at and above 3.3.2 have this blocker, thus `emerge -1 '<dev-lang/python-3.3.2-r2'` for a start).
When you do decide to downgrade dev-lang/python that way; you'll also need to depclean the newer version, as well as set PYTHON_TARGETS in /etc/portage/make.conf in a way that doesn't pull in 3.3 or 3.4.
For example: PYTHON_TARGETS="python2_7 python3_2" |
|
| Back to top |
|
|
wrc1944
Advocate
Joined: 15 Aug 2002
Posts: 3435
Location: Gainesville, Florida
|
| Posted: Wed Mar 26, 2014 12:28 pm Post subject: |
|
|
dol-sen fixed the emerge problem with the portage-2.2.10.
I'm still wondering if ~Arch users should remove python-3.2 and go with PYTHON_TARGETS="python2_7 python3_3"
Weren't there problems with 3.2? Seems I read that somewhere, but since I've always had 2.7 set as default I never thought much about it- everything was always working fine.
_________________
Main box- AsRock x370 Gaming K4
Ryzen 7 3700x, 3.6GHz, 16GB GSkill Flare DDR4 3200mhz
Samsung SATA 1000GB, Radeon HD R7 350 2GB DDR5
OpenRC Gentoo ~amd64 plasma, glibc-2.36-r7, gcc-13.2.1_p20230304
kernel-6.8.4 USE=experimental python3_11 |
|
| Back to top |
|
|
TomWij
Retired Dev
Joined: 04 Jul 2012
Posts: 1553
|
| Posted: Wed Mar 26, 2014 12:53 pm Post subject: |
|
|
| No idea, I have a lot of versions set there without problems (on ~amd64). |
|
| Back to top |
|
|
ulenrich
Veteran
Joined: 10 Oct 2010
Posts: 1480
|
| Posted: Wed Mar 26, 2014 1:04 pm Post subject: |
|
|
| wrc1944 wrote: | dol-sen fixed the emerge problem with the portage-2.2.10.
I'm still wondering if ~Arch users should remove python-3.2 and go with PYTHON_TARGETS="python2_7 python3_3" |
IMHO don't wonder but do it if Gentoo~current. As soon as there was a python-3.3 stable version no question  |
|
| Back to top |
|
|
|
Portage & Programming
