1 |
On Wed, Oct 30, 2019 at 09:19:14PM +1300, Kent Fredric wrote: |
2 |
> On Tue, 29 Oct 2019 12:27:49 -0500 |
3 |
> William Hubbs <williamh@g.o> wrote: |
4 |
> |
5 |
> > No, I'm just saying this: |
6 |
> > |
7 |
> > 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. |
8 |
> > |
9 |
> > --with-bdeps=y is the default for a good reason as far as I am aware. |
10 |
> > |
11 |
> > William |
12 |
> |
13 |
> It only took a 3 days, but today, I'm helping a user who has a massive upgrade problem. |
14 |
> |
15 |
> Among it, is this gem of a "conflict" |
16 |
> |
17 |
> |
18 |
> dev-python/setuptools:0 |
19 |
> |
20 |
> (dev-python/setuptools-41.1.0:0/0::gentoo, ebuild scheduled for merge) pulled in by |
21 |
> 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) |
22 |
> |
23 |
> 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) |
24 |
> |
25 |
> |
26 |
> (dev-python/setuptools-20.6.7:0/0::gentoo, installed) pulled in by |
27 |
> 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) |
28 |
> |
29 |
> 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) |
30 |
> |
31 |
> 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) |
32 |
> |
33 |
> 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) |
34 |
> |
35 |
> 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) |
36 |
> |
37 |
> Why the hell is this happening? |
38 |
> |
39 |
> Oh. Because portage is blocking upgrading something because they're |
40 |
> pulled into the graph by --with-bdeps=y |
41 |
> |
42 |
> Passing --with-bdeps=n removes half of these conflicts ( but not all, |
43 |
> but thats probably some other problem, but I have no idea -what- |
44 |
> because portage refuses to tell me ) |
45 |
|
46 |
You're right, I hate these kinds of error messages. I would go so far as |
47 |
to say they are useless and the way this is handled should be cleaned |
48 |
up. |
49 |
|
50 |
I don't know portage internals, so I have no idea what the deal with |
51 |
this is or how to fix it. |
52 |
|
53 |
Did you report it to the portage team? |
54 |
|
55 |
> Portage just ain't bothered to try upgrading them properly, and ain't |
56 |
> smart enough to know that this is not an issue in the first place. |
57 |
> |
58 |
> But I'd bet the remaining ones are "somebody did it wrong once upon a |
59 |
> time, but the user sill has installed copies of the packages where it |
60 |
> was done wrong" |
61 |
> |
62 |
> But stupid portage is escallating *everything* to this stupid standard. |
63 |
> |
64 |
> Which is garbage, because "upgrade setuptools" should in no way break |
65 |
> *anything* that is currently installed, let alone, something like x264 |
66 |
> ( which was the target problem at the time of trying to fix this ) |
67 |
> |
68 |
> And portage just *isnt* smart enough to fix this on its own. |
69 |
> |
70 |
> Please spend more time helping users in #gentoo, you will see messes |
71 |
> like this on a *daily* basis. |
72 |
|
73 |
I've noticed it gets messy very quickly if you wait a while to upgrade |
74 |
your system also, so I would be curious how long the user waited to do |
75 |
an upgrade? |
76 |
|
77 |
Python is also more complex than most things because we allow multiple |
78 |
versions. |
79 |
|
80 |
There's no way to know whether removing virtual/rust will cause these |
81 |
kinds of issues, so I'm still not convinced that we shouldn't remove it. |
82 |
|
83 |
William |