1 |
On Thu, Jun 25, 2020 at 11:07 PM Aaron Bauman <bman@g.o> wrote: |
2 |
> |
3 |
> On Wed, Jun 24, 2020 at 04:21:14PM -0400, Rich Freeman wrote: |
4 |
> > |
5 |
> > We're removing python2 around <date>. You can help us out by updating |
6 |
> > any packages you have that use python2. If you want to easily |
7 |
> > identify these packages just do <insert quick script here>. |
8 |
> > |
9 |
> > I think the problem here is that we're basically telling maintainers |
10 |
> > that the beatings will continue until morale improves. Then we're |
11 |
> > wondering why nothing is getting done. |
12 |
> > |
13 |
> |
14 |
> I am thoroughly confused here. Some how you have completely changed your |
15 |
> opinion from previous posts. |
16 |
|
17 |
Perhaps we failed to communicate then. My opinion has always been this: |
18 |
|
19 |
I support letting the python team manage the versions of python |
20 |
available - if people want legacy versions to stick around they need |
21 |
to do something to make it happen. |
22 |
|
23 |
HOWEVER, the python team would also find its job much easier if they |
24 |
partnered with the myriad of package maintainers to accomplish their |
25 |
goals, instead of just throwing them over the fence and then breaking |
26 |
things for users to try to get everybody's attention periodically. |
27 |
|
28 |
> |
29 |
> Of all the methods listed in the previous posts, the QA reports, etc. |
30 |
> there is no excuse individuals can't find out if their package is py2 |
31 |
> only. |
32 |
|
33 |
None of those methods were posted until a day or two ago, and the |
34 |
python team has done nothing to actually ensure all the impacted |
35 |
maintainers are aware of them. Perhaps a communication to |
36 |
-dev-announce with the preferred approach would be better? |
37 |
|
38 |
You can't expect every Gentoo dev to independently cobble together a |
39 |
bunch of scripts to go hunting for py2 reverse deps. |
40 |
|
41 |
> Ironically, it would be a very sad state if an individual doesn't know |
42 |
> what Python interpreter their package is compatible with. This is the |
43 |
> essence of "maintainer" status, correct? |
44 |
|
45 |
Maintainers generally care about what the package does, and how it |
46 |
does it is a means to an end. Sure, some care more about the build |
47 |
system and dependencies than others, and when working on a package you |
48 |
need to pay more attention to such things. However, I suspect most |
49 |
package maintainers do not know off the top of their head the |
50 |
dependency list of all their packages. |
51 |
|
52 |
> Obviously, the myriad of tools, ML threads, and all the other "avenues" |
53 |
> individual developers have taken to alert others simply doesn't work... |
54 |
> until something is p.masked... people don't budge. |
55 |
|
56 |
At least some devs here seemed surprised about the masks. Did you try |
57 |
filing a bug? |
58 |
|
59 |
Masking something for all users is basically like torturing a kitten |
60 |
to get the attention of its owner. It is a necessary step if the |
61 |
package is actually to be removed. I don't think it is even allowable |
62 |
under our policies if no bug was filed. |
63 |
|
64 |
But if filing bugs is painful at least make things easier on |
65 |
maintainers. Post a list of packages and owners, for example. |
66 |
|
67 |
It just seems like you're making things harder on yourself. Gentoo |
68 |
has done countless migrations like this and for whatever reason in the |
69 |
past creating a tracker and blocker bugs hasn't been a problem. |
70 |
|
71 |
I don't think the community will be served by having the python team |
72 |
work itself into a frenzy until they ragequit. Just give in, send out |
73 |
a -announce post, and maybe cut your workload in half at least. I get |
74 |
that you seem to want to stand on some kind of principle that |
75 |
everybody in Gentoo should care about the py2 migration as much as you |
76 |
do, but it probably isn't going to happen. Help everybody else help |
77 |
you... |
78 |
|
79 |
-- |
80 |
Rich |