| 1 |
On Tue, 29 Oct 2019 12:27:49 -0500 |
| 2 |
William Hubbs <williamh@g.o> wrote: |
| 3 |
|
| 4 |
> No, I'm just saying this: |
| 5 |
> |
| 6 |
> We don't know that there is a portage bug from what I'm reading in this thread. We are talking about possible bugs, but a possible bug isn't a bug. If there is an issue cite it otherwise move on. |
| 7 |
> |
| 8 |
> --with-bdeps=y is the default for a good reason as far as I am aware. |
| 9 |
> |
| 10 |
> William |
| 11 |
|
| 12 |
It only took a 3 days, but today, I'm helping a user who has a massive upgrade problem. |
| 13 |
|
| 14 |
Among it, is this gem of a "conflict" |
| 15 |
|
| 16 |
|
| 17 |
dev-python/setuptools:0 |
| 18 |
|
| 19 |
(dev-python/setuptools-41.1.0:0/0::gentoo, ebuild scheduled for merge) pulled in by |
| 20 |
dev-python/setuptools[python_targets_python3_5(-)?,python_targets_python3_6(-)?,python_targets_python3_7(-)?,-python_single_target_python3_5(-),-python_single_target_python3_6(-),-python_single_target_python3_7(-)] required by (dev-util/meson-0.51.2:0/0::gentoo, ebuild scheduled for merge) |
| 21 |
|
| 22 |
dev-python/setuptools[python_targets_pypy(-)?,python_targets_pypy3(-)?,python_targets_python2_7(-)?,python_targets_python3_5(-)?,python_targets_python3_6(-)?,python_targets_python3_7(-)?,-python_single_target_pypy(-),-python_single_target_pypy3(-),-python_single_target_python2_7(-),-python_single_target_python3_5(-),-python_single_target_python3_6(-),-python_single_target_python3_7(-)] required by (dev-python/certifi-2019.6.16:0/0::gentoo, ebuild scheduled for merge) |
| 23 |
|
| 24 |
|
| 25 |
(dev-python/setuptools-20.6.7:0/0::gentoo, installed) pulled in by |
| 26 |
dev-python/setuptools[python_targets_python2_7(-),python_targets_python3_4(-),-python_single_target_python2_7(-),-python_single_target_python3_3(-),-python_single_target_python3_4(-),-python_single_target_python3_5(-)] required by (net-misc/youtube-dl-2016.09.19:0/0::gentoo, installed) |
| 27 |
|
| 28 |
dev-python/setuptools[python_targets_python2_7(-),python_targets_python3_4(-),-python_single_target_pypy(-),-python_single_target_pypy3(-),-python_single_target_python2_7(-),-python_single_target_python3_3(-),-python_single_target_python3_4(-),-python_single_target_python3_5(-)] required by (dev-python/jinja-2.8:0/0::gentoo, installed) |
| 29 |
|
| 30 |
dev-python/setuptools[python_targets_python2_7(-),python_targets_python3_4(-),-python_single_target_python2_7(-),-python_single_target_python3_3(-),-python_single_target_python3_4(-),-python_single_target_python3_5(-)] required by (dev-python/numpy-1.10.4:0/0::gentoo, installed) |
| 31 |
|
| 32 |
dev-python/setuptools[python_targets_python2_7(-),python_targets_python3_4(-),-python_single_target_pypy(-),-python_single_target_pypy3(-),-python_single_target_python2_7(-),-python_single_target_python3_3(-),-python_single_target_python3_4(-),-python_single_target_python3_5(-)] required by (dev-python/certifi-2015.11.20:0/0::gentoo, installed) |
| 33 |
|
| 34 |
dev-python/setuptools[python_targets_python2_7(-),python_targets_python3_4(-),-python_single_target_pypy(-),-python_single_target_pypy3(-),-python_single_target_python2_7(-),-python_single_target_python3_3(-),-python_single_target_python3_4(-),-python_single_target_python3_5(-)] required by (dev-python/pygments-2.1.1:0/0::gentoo, installed) |
| 35 |
|
| 36 |
Why the hell is this happening? |
| 37 |
|
| 38 |
Oh. Because portage is blocking upgrading something because they're |
| 39 |
pulled into the graph by --with-bdeps=y |
| 40 |
|
| 41 |
Passing --with-bdeps=n removes half of these conflicts ( but not all, |
| 42 |
but thats probably some other problem, but I have no idea -what- |
| 43 |
because portage refuses to tell me ) |
| 44 |
|
| 45 |
Portage just ain't bothered to try upgrading them properly, and ain't |
| 46 |
smart enough to know that this is not an issue in the first place. |
| 47 |
|
| 48 |
But I'd bet the remaining ones are "somebody did it wrong once upon a |
| 49 |
time, but the user sill has installed copies of the packages where it |
| 50 |
was done wrong" |
| 51 |
|
| 52 |
But stupid portage is escallating *everything* to this stupid standard. |
| 53 |
|
| 54 |
Which is garbage, because "upgrade setuptools" should in no way break |
| 55 |
*anything* that is currently installed, let alone, something like x264 |
| 56 |
( which was the target problem at the time of trying to fix this ) |
| 57 |
|
| 58 |
And portage just *isnt* smart enough to fix this on its own. |
| 59 |
|
| 60 |
Please spend more time helping users in #gentoo, you will see messes |
| 61 |
like this on a *daily* basis. |
Archives