| 1 |
On Sep 16, 2012 1:05 PM, "Andrew Lowe" <agl@×××××××.au> wrote: |
| 2 |
> |
| 3 |
> Hi all, |
| 4 |
> I've got a media server that I'm in the process of installing |
| 5 |
Samba on. When I do: |
| 6 |
> |
| 7 |
> emerge -NuD --pretend samba |
| 8 |
> |
| 9 |
> I get a list of stuff that portage wants to install, including Python, |
| 10 |
V2.7.3, even though the machine already has V3.2.3 installed. I've also |
| 11 |
stripped down the USE variables to basically "server" and that's all and |
| 12 |
still for some reason portage wants to bring in Python - the older version, |
| 13 |
V2. I've even added a "-python" to packages.use and it still wants python, |
| 14 |
V2. I've had a look at the USE variables for the packages that follow |
| 15 |
Python in the emerge list and they either don't want python or already have |
| 16 |
"-python" set. |
| 17 |
> |
| 18 |
> Having a play around with equery also didn't reveal anything. |
| 19 |
Does anyone have any ideas as to what's causing old Python to be brought |
| 20 |
in? I haven't posted the whole "emerge --info" stuff yet as hopefully |
| 21 |
someone has come across this problem before. |
| 22 |
> |
| 23 |
> Any thoughts greatly appreciated, |
| 24 |
> |
| 25 |
> Andrew |
| 26 |
> |
| 27 |
|
| 28 |
Hi, when you are dealing with python always remember that the API has |
| 29 |
changed between version 2 and 3 so python 3 can't handle python 2 scripts. |
| 30 |
|
| 31 |
So what I think emerge is doing here is installing python 2.7 beside 3.2. |
| 32 |
|
| 33 |
When you add the verbose flag to the emerge command, you will probably see |
| 34 |
something like [ NS ] or [ uS ] at the beginning of the python line. The S |
| 35 |
stands for new slot, so both version will be installedbecause samba or one |
| 36 |
of it's dependency is using python 2 scripts. |
| 37 |
|
| 38 |
Mit freundlichen Grüßen / Best Regards |
| 39 |
|
| 40 |
Randolph Maaßen |
Archives