On 2022.07.05 12:43, Grant Edwards wrote:
On 2022-07-05, 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:
>> 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.
I've tried that, and it takes forever. Everything time you do it, the
next emerge attempt will fail because one of that package's
dependencies doesn't have 3_9 set. So you set that one, do an emerge,
and it fails because there's another depenency that doesn't have 3_9
set. Repeat this for an hour or two...
If it would tell you about all of them at once, it wouldn't be so bad.
But, if you're trying to hold back a large application with dozens and
dozens of dependancies it makes you want to scream.
Or doesn't it torture you like that any longer?
Oh, it still does. I just think I anticipate it more often, so I am
frequently able to deal with more than one "layer" in each round, so
the total process doesn't take so long. I've run into problems both
for dependencies of the package I changed first, and packages for which
It is a dependency.
On major updates, such as KDE, emerge @world often shows me a long list
of packages it will upgrade, followed by a long list of slot
conflicts. Over the years I've not necessarily gotten better at
directly interpreting portage's output, but at least figuring out I've
got one package somehow related to the ones to be upgraded (usually
somewhere in the dependency tree) which itself doesn't have an upgrade,
but does need to be rebuilt at the same time. I'll often end up doing
"eix-installed -a | grep kde" (or python) and look for a package that
isn't being upgraded, but is in the dependency tree of one or more
which is. It is also common that the problem is a package I've added
under /etc/portage, and I just need to figure out if it still needs to
be there, or else how that non-standard entry affects other packages.
