| 1 |
On Sun, 24 Mar 2019 23:12:36 +0000, Mick wrote: |
| 2 |
|
| 3 |
> > > stopped appearing on my "emerge update world" commands. Perhaps you |
| 4 |
> > > Neil tested further for failure and Jack and I should as well. |
| 5 |
> > |
| 6 |
> > No, I tested exactly the same: |
| 7 |
> > |
| 8 |
> > emerge world gives warning |
| 9 |
> > run eselect python cleanup |
| 10 |
> > emerge world gives warning |
| 11 |
> > run eselect python cleanup |
| 12 |
> > emerge world gives no warning |
| 13 |
> > |
| 14 |
> > I should have examined /etc/python-exec/python-exec.conf beforehand, |
| 15 |
> > maybe it included two mentions of python3.4. |
| 16 |
> |
| 17 |
> In my case /etc/python-exec/python-exec.conf included python 3.4 and |
| 18 |
> 3.5, while 'eselect python list' showed them as "(uninstalled)". After |
| 19 |
> running 'eselect python cleanup' only 3.6 is shown now in |
| 20 |
> python-exec.conf, although python list also shows 2.7 as a fallback. |
| 21 |
|
| 22 |
|
| 23 |
Both warnings were about python3.4. Looking at a btrfs snapshot from |
| 24 |
yesterday, I see what happened. python-exec.conf contained |
| 25 |
|
| 26 |
python2.7 |
| 27 |
python3.5 |
| 28 |
python3.6 |
| 29 |
python3.4 |
| 30 |
|
| 31 |
I only have 2.7 and 3.6 installed. Running eselect clean the first time |
| 32 |
must have removed only the pythong3.5 entry, hence the identical warning |
| 33 |
about 3.4, then that entry was removed on the second run. It appears, as |
| 34 |
suggested elsewhere, that eselect python clean cleans only one entry at a |
| 35 |
time. |
| 36 |
|
| 37 |
|
| 38 |
-- |
| 39 |
Neil Bothwick |
| 40 |
|
| 41 |
Nobody's perfect and since I'm nobody...! |
Archives