| 1 |
On Thursday, May 7, 2020 5:43 AM, Rich Freeman <rich0@g.o> wrote: |
| 2 |
|
| 3 |
> Are you overriding something, or were you running this right in the |
| 4 |
> middle of an update? |
| 5 |
|
| 6 |
emerge was updating, then some ebuild failed and i |
| 7 |
didn't have --keep-going. then next time i tried |
| 8 |
to sync layman it failed. |
| 9 |
|
| 10 |
i'm now re-running emerge and it seems to work |
| 11 |
normally. |
| 12 |
|
| 13 |
> |
| 14 |
> layman-2.4.2 strictly requires python 3.6 and the system wouldn't let |
| 15 |
> you remove that version of python unless you forced it to. The newer |
| 16 |
> version of layman is compatible with the newer versions of python, but |
| 17 |
> of course needs to be rebuilt for it. |
| 18 |
|
| 19 |
i have layman-2.4.3, emerged with python3_6, and |
| 20 |
is now about to be moved to python3_7. |
| 21 |
|
| 22 |
no biggie. i can fix it. but, my point is, this |
| 23 |
hassle is needless and keeps coming. |
| 24 |
|
| 25 |
> If you read the news on the update you'd see this. If you just do a |
| 26 |
> regular emerge -uD @world then while it was in the middle of updating |
| 27 |
> some things would break. There are instructions in the news for how |
| 28 |
> to do a more seamless upgrade by enabling both the older and newer |
| 29 |
> versions of python in parallel, in which case there won't be any point |
| 30 |
> where things break. That does require rebuilding everything twice |
| 31 |
> (not necessarily at the same time). |
| 32 |
|
| 33 |
true, but needless hassle imo. |
| 34 |
|
| 35 |
> Really though this is pretty tame. There have been some updates to |
| 36 |
> expat and especially glibc in the past that were pretty hairy. |
| 37 |
|
| 38 |
are you referring to python's dependence on expat |
| 39 |
and glibc? |
| 40 |
|
| 41 |
yeah, so many layers of mistakes get born when one |
| 42 |
relies on python as a dependency for a system app |
| 43 |
that manages other apps (including itself). |
Archives