On Tue, Jul 5, 2022 at 12:36 PM Jack <ostrof...@users.sourceforge.net> wrote: > > On 2022.07.05 12:24, Grant Edwards wrote: > > On 2022-07-05, William Kenworthy <bi...@iinet.net.au> wrote: > > > > > I synced portage a couple of days now and now my systems are > > rebuilding > > > python modules for 3.10 without any input from me [...] > > > > Every time there's a Python upgrade like this, it turns into a bit of > > an ordeal because I always have a small handful of packages that don't > > support the newer version. > > > > The news item offers no advice on what to do in this situation other > > than completely postponing the upgrade of everything (which doesn't > > seem like the best choice.) > > > > It would be nice if the news item explained how to let the upgrade > > procede while holding back a few packages. > > > > Can you set 3_9 and 3_10 globally, and then disable 3_10 for a few > > individual packages that can't be built with 3_10? > As far as I can tell, you just need to add python_targets_python3_9 for > the package in the appropriate package.use file. >
That and its dependencies. Obviously you need to be caught up before things get removed from the repo, but the offending package itself will get removed when that happens anyway. You can always just globally keep the older version around longer if you don't want to deal with a bunch of cruft in /etc/portage/package.use. The news item explains how to do this. -- Rich
