View previous topic :: View next topic |
Author |
Message |
siknasa9 n00b
Joined: 09 Dec 2011 Posts: 62
|
Posted: Wed Sep 18, 2013 10:56 pm Post subject: Requiring rhythmbox-3.0-r1 but python3_2 single target... |
|
|
I am just wondering why this is so necessary that I can't even mask it. I installed rhythmbox-2.99.1 and added 3.0-r1 to package.mask and portage still tries to install it. It's asking for me to make PYTHON_SINGLE_TARGET="python3_2" but it conflicts with other packages. Is there something I'm missing or a way around it? _________________ Autobots... roll out!! |
|
Back to top |
|
|
fturco Veteran
Joined: 08 Dec 2010 Posts: 1181 Location: Italy
|
Posted: Thu Sep 19, 2013 6:42 am Post subject: |
|
|
I created the /etc/portage/env/rhythmbox.conf file with:
Code: | PYTHON_SINGLE_TARGET="python3_2" |
Then added the following line to /etc/portage/package.env:
Code: | =media-sound/rhythmbox-3.0-r1 rhythmbox.conf |
I don't really know what the PYTHON_SINGLE_TARGET variable is or how to deal with different Python versions, but it seems to work for me. |
|
Back to top |
|
|
siknasa9 n00b
Joined: 09 Dec 2011 Posts: 62
|
Posted: Sat Sep 21, 2013 3:17 am Post subject: |
|
|
fturco wrote: | I created the /etc/portage/env/rhythmbox.conf file with:
Code: | PYTHON_SINGLE_TARGET="python3_2" |
Then added the following line to /etc/portage/package.env:
Code: | =media-sound/rhythmbox-3.0-r1 rhythmbox.conf |
I don't really know what the PYTHON_SINGLE_TARGET variable is or how to deal with different Python versions, but it seems to work for me. |
Perfect!! Thanks so much, fturco. _________________ Autobots... roll out!! |
|
Back to top |
|
|
|