Gentoo Archives: gentoo-dev

From: Aaron Bauman <bman@g.o>
To: gentoo-dev@l.g.o
Subject: Re: [gentoo-dev] */*: Mask Py2 only packages
Date: Fri, 26 Jun 2020 14:36:33
Message-Id: A0DFBECE-CF3C-4761-B375-27DA58E2D75A@gentoo.org
In Reply to: Re: [gentoo-dev] */*: Mask Py2 only packages by Rich Freeman
1 On June 26, 2020 7:13:07 AM EDT, Rich Freeman <rich0@g.o> wrote:
2 >On Thu, Jun 25, 2020 at 11:07 PM Aaron Bauman <bman@g.o> wrote:
3 >>
4 >> On Wed, Jun 24, 2020 at 04:21:14PM -0400, Rich Freeman wrote:
5 >> >
6 >> > We're removing python2 around <date>. You can help us out by
7 >updating
8 >> > any packages you have that use python2. If you want to easily
9 >> > identify these packages just do <insert quick script here>.
10 >> >
11 >> > I think the problem here is that we're basically telling
12 >maintainers
13 >> > that the beatings will continue until morale improves. Then we're
14 >> > wondering why nothing is getting done.
15 >> >
16 >>
17 >> I am thoroughly confused here. Some how you have completely changed
18 >your
19 >> opinion from previous posts.
20 >
21 >Perhaps we failed to communicate then. My opinion has always been
22 >this:
23 >
24 >I support letting the python team manage the versions of python
25 >available - if people want legacy versions to stick around they need
26 >to do something to make it happen.
27 >
28 >HOWEVER, the python team would also find its job much easier if they
29 >partnered with the myriad of package maintainers to accomplish their
30 >goals, instead of just throwing them over the fence and then breaking
31 >things for users to try to get everybody's attention periodically.
32 >
33
34 How have we *not* partnered with the community of devs? Michal's mails to the list? Previous discussions based on masks...
35
36 >>
37 >> Of all the methods listed in the previous posts, the QA reports, etc.
38 >> there is no excuse individuals can't find out if their package is py2
39 >> only.
40 >
41 >None of those methods were posted until a day or two ago, and the
42 >python team has done nothing to actually ensure all the impacted
43 >maintainers are aware of them. Perhaps a communication to
44 >-dev-announce with the preferred approach would be better?
45 >
46
47 You should also look at qa-reports. Do we really need to *teach* others "how to fish" here? Why can't folks just ask for assistance?
48
49 All of it has been there and widely available for quite some time. Stop finding excuses.
50
51 >You can't expect every Gentoo dev to independently cobble together a
52 >bunch of scripts to go hunting for py2 reverse deps.
53 >
54
55 See above. Qa-reports will output a very nice list (even a graphic!) of such things. Anyway, yes, I do expect devs to understand their packages state if they maintain it. Don't be so myopic.
56
57 >> Ironically, it would be a very sad state if an individual doesn't
58 >know
59 >> what Python interpreter their package is compatible with. This is the
60 >> essence of "maintainer" status, correct?
61 >
62 >Maintainers generally care about what the package does, and how it
63 >does it is a means to an end. Sure, some care more about the build
64 >system and dependencies than others, and when working on a package you
65 >need to pay more attention to such things. However, I suspect most
66 >package maintainers do not know off the top of their head the
67 >dependency list of all their packages.
68 >
69 >> Obviously, the myriad of tools, ML threads, and all the other
70 >"avenues"
71 >> individual developers have taken to alert others simply doesn't
72 >work...
73 >> until something is p.masked... people don't budge.
74 >
75 >At least some devs here seemed surprised about the masks. Did you try
76 >filing a bug?
77
78 Have you looked for said bugs?
79
80 >
81 >Masking something for all users is basically like torturing a kitten
82 >to get the attention of its owner. It is a necessary step if the
83 >package is actually to be removed. I don't think it is even allowable
84 >under our policies if no bug was filed.
85 >
86
87 Do tell where said policy is?
88
89 >But if filing bugs is painful at least make things easier on
90 >maintainers. Post a list of packages and owners, for example.
91 >
92 >It just seems like you're making things harder on yourself. Gentoo
93 >has done countless migrations like this and for whatever reason in the
94 >past creating a tracker and blocker bugs hasn't been a problem.
95 >
96
97 Nothing is really hard about masking packages for removal... honestly. The work comes in defending the position here for the few that complain. If I filed a bug... they would complain or not respond... If I sent out a dev-announce they would complain or not respond.
98
99 You see the fun here? Which method is effective? Mask a 100 packages for removal... Someone complains... A few packages get saved and 90 get removed... Life goes on.
100
101 -Aaron
102
103 --
104 Sent from my Android device with K-9 Mail. Please excuse my brevity.

Replies

Subject Author
Re: [gentoo-dev] */*: Mask Py2 only packages Rich Freeman <rich0@g.o>