| 1 |
On 2022.07.05 12:43, Grant Edwards wrote: |
| 2 |
> On 2022-07-05, Jack <ostroffjh@×××××××××××××××××.net> wrote: |
| 3 |
> > On 2022.07.05 12:24, Grant Edwards wrote: |
| 4 |
> >> On 2022-07-05, William Kenworthy <billk@×××××××××.au> wrote: |
| 5 |
> |
| 6 |
> >> It would be nice if the news item explained how to let the upgrade |
| 7 |
> >> procede while holding back a few packages. |
| 8 |
> >> |
| 9 |
> >> Can you set 3_9 and 3_10 globally, and then disable 3_10 for a few |
| 10 |
> >> individual packages that can't be built with 3_10? |
| 11 |
> |
| 12 |
> > As far as I can tell, you just need to add python_targets_python3_9 |
| 13 |
> for |
| 14 |
> > the package in the appropriate package.use file. |
| 15 |
> |
| 16 |
> I've tried that, and it takes forever. Everything time you do it, the |
| 17 |
> next emerge attempt will fail because one of that package's |
| 18 |
> dependencies doesn't have 3_9 set. So you set that one, do an emerge, |
| 19 |
> and it fails because there's another depenency that doesn't have 3_9 |
| 20 |
> set. Repeat this for an hour or two... |
| 21 |
> |
| 22 |
> If it would tell you about all of them at once, it wouldn't be so bad. |
| 23 |
> But, if you're trying to hold back a large application with dozens and |
| 24 |
> dozens of dependancies it makes you want to scream. |
| 25 |
> |
| 26 |
> Or doesn't it torture you like that any longer? |
| 27 |
Oh, it still does. I just think I anticipate it more often, so I am |
| 28 |
frequently able to deal with more than one "layer" in each round, so |
| 29 |
the total process doesn't take so long. I've run into problems both |
| 30 |
for dependencies of the package I changed first, and packages for which |
| 31 |
It is a dependency. |
| 32 |
|
| 33 |
On major updates, such as KDE, emerge @world often shows me a long list |
| 34 |
of packages it will upgrade, followed by a long list of slot |
| 35 |
conflicts. Over the years I've not necessarily gotten better at |
| 36 |
directly interpreting portage's output, but at least figuring out I've |
| 37 |
got one package somehow related to the ones to be upgraded (usually |
| 38 |
somewhere in the dependency tree) which itself doesn't have an upgrade, |
| 39 |
but does need to be rebuilt at the same time. I'll often end up doing |
| 40 |
"eix-installed -a | grep kde" (or python) and look for a package that |
| 41 |
isn't being upgraded, but is in the dependency tree of one or more |
| 42 |
which is. It is also common that the problem is a package I've added |
| 43 |
under /etc/portage, and I just need to figure out if it still needs to |
| 44 |
be there, or else how that non-standard entry affects other packages. |
Archives