| 1 |
On Wed, Dec 7, 2016 at 1:37 PM, allan gottlieb <gottlieb@×××.edu> wrote: |
| 2 |
|
| 3 |
> I can't complete an emerge @preserved-rebuild due to the lack of |
| 4 |
> python3.3. |
| 5 |
> |
| 6 |
> However, I read the news article and have set the python3 interpreter to |
| 7 |
> python3.4 |
| 8 |
> |
| 9 |
> allan ~ # eselect python list --python3 |
| 10 |
> Available Python 3 interpreters: |
| 11 |
> [1] python3.3 |
| 12 |
> [2] python3.4 * |
| 13 |
> allan ~ # eselect python list |
| 14 |
> Available Python interpreters: |
| 15 |
> [1] python2.7 * |
| 16 |
> [2] python3.3 |
| 17 |
> [3] python3.4 |
| 18 |
> allan ~ # |
| 19 |
> |
| 20 |
> Here is the output from emerge @preserved-rebuild |
| 21 |
> |
| 22 |
> allan ~ # emerge @preserved-rebuild |
| 23 |
> |
| 24 |
> These are the packages that would be merged, in reverse order: |
| 25 |
> |
| 26 |
> Calculating dependencies... done! |
| 27 |
> |
| 28 |
> emerge: there are no ebuilds to satisfy "dev-lang/python:3.3". |
| 29 |
> (dependency required by "@preserved-rebuild" [argument]) |
| 30 |
> |
| 31 |
|
| 32 |
Something appears to want 3.3 specifically, not 3.x. Try adding -v to |
| 33 |
emerge to try to work out which package it is, then check the ebuilds of |
| 34 |
other versions to see if there's one that's not dependent on 3.3. |
Archives