1 |
On Mon, 2021-05-03 at 19:06 +0100, Sam James wrote: |
2 |
> |
3 |
> > On 2 May 2021, at 23:04, Michał Górny <mgorny@g.o> wrote: |
4 |
> > [snip] |
5 |
> > +Upgrade commands |
6 |
> > +================ |
7 |
> > +The Python 3.8 cleanup requires that Python 3.8 is removed from complete |
8 |
> > +dependency trees in batch. If some of the installed packages using |
9 |
> > +an older Python version are not triaged for the upgrade, the package |
10 |
> > +manager will throw dependency conflicts. This makes it important that |
11 |
> > +the upgrade is carried via a --deep --changed-use @world upgrade, |
12 |
> > +as well as that any stray packages are removed prior to it, e.g.: |
13 |
> > + |
14 |
> > + emerge --depclean |
15 |
> > + emerge -1vUD @world |
16 |
> > + emerge --depclean |
17 |
> |
18 |
> |
19 |
> Only suggestion: we put this at the top and suggest people do it immediately |
20 |
> on the switchover day, and ideally beforehand to minimise possible conflicts |
21 |
> (so their system is in good state beforehand). |
22 |
|
23 |
I want to avoid it on the top, so people don't do it prematurely before |
24 |
reading their options. |
25 |
|
26 |
-- |
27 |
Best regards, |
28 |
Michał Górny |