Timeline for Arch Linux: python and python2 are in conflict
Current License: CC BY-SA 2.5
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 21, 2011 at 3:44 | vote | accept | Blender | ||
| Mar 10, 2011 at 13:33 | comment | added | mattdm | Ah, right, that makes perfect sense. Thanks. | |
| Mar 10, 2011 at 13:29 | comment | added | gnud |
And the python2 package is getting pulled in by one of the packages in the compiz-fusion-gtk group.
|
|
| Mar 10, 2011 at 13:29 | comment | added | gnud |
That conflict is coming from the python2 package, which is (naturally) in conflict with older python packages. Upgrade python first, and all should be well, hopefully.
|
|
| Mar 10, 2011 at 13:17 | comment | added | mattdm | Ahh, the nuances of packaging systems. So where is "python and python2 are in conflict (python<3). Remove python2?" coming from? | |
| Mar 10, 2011 at 13:13 | comment | added | gnud |
No. Updated packages requiring python 2 will specify a dependency on python2. Updated packages requiring python 3 will specify a dependency on python. Specifying a conflict with python<3 is just a way to force you to update your system before installing, I guess.
|
|
| Mar 10, 2011 at 13:10 | comment | added | mattdm |
So, is it the updated python ( that is, python 3) which is set to conflict with python<3, or is it compiz-fusion-gtk doing that? If it's the new python, that leaves @Blender out of luck, as long as anything still requires python2, right?
|
|
| Mar 10, 2011 at 9:01 | history | answered | gnud | CC BY-SA 2.5 |