Gentoo Archives: gentoo-dev

From: David Seifert <soap@g.o>
To: gentoo-dev@l.g.o
Subject: Re: [gentoo-dev] [PATCH] metadata/install-qa-check.d: add 60tmpfiles-path QA check
Date: Fri, 13 Aug 2021 11:04:38
Message-Id: d79b3c2966262d366c18378bc1cdbb7af065cc70.camel@gentoo.org
In Reply to: Re: [gentoo-dev] [PATCH] metadata/install-qa-check.d: add 60tmpfiles-path QA check by Thomas Deutschmann
1 On Mon, 2021-08-09 at 19:50 +0200, Thomas Deutschmann wrote:
2 > On 2021-08-08 13:17, David Seifert wrote:
3 > > So you've created a big commotion... because you didn't get the
4 > > initial
5 > > point? Honestly, this seems to be a recurring theme at this point.
6 > > Someone suggests some improved check/some change, and nowadays you
7 > > can
8 > > bet 50 quid that Whissi will pop up and bikeshed it in some way.
9 >
10 > No?
11 >
12 > First of all, just because you disagree with something or believe a
13 > discussion is wrong and or not necessary and start to frame it as
14 > bikeshedding, it doesn't actually become bikeshedding. This is a very
15 > sad and transparent attempt to silence people through defamation.
16 >
17 > The draft contains an error. It's saying that "/etc/tmpfiles.d" became
18 > deprecated which is not true. Because this would imply that it was
19 > previously acceptable for packages in Gentoo repository to install to
20 > that location which is not correct. If a packages in ::gentoo
21 > installed
22 > to /etc/tmpfiles.d before, this was already wrong.
23 >
24 > And my point was and still is, that neither the commit message nor the
25 > eqawarn should use the wording "deprecated" because nothing has
26 > changed
27 > -- no location became deprecated.
28 >
29 > And this will also address parts of antarus' previous mail: Because
30 > this
31 > QA check should be only about ::gentoo repository, this shouldn't
32 > affect
33 > any other repository. I.e. in your own overlay, you are free to do
34 > whatever you want and can't be forced to stick to Gentoo QA rules.
35 >
36 >
37 > > It's become a real problem at this point. In fact, we have proxy
38 > > maintainers publicly refusing to work on packages somehow involving
39 > > you
40 > > (I'll mention no names, but check the #-desktop backlog), because
41 > > your
42 > > personality boils down to three attributes nowadays:
43 >
44 > I am not in that channel and never was. If you make such an
45 > allegation,
46 > include facts so that I can respond. If you look at my complete
47 > history
48 > at GitHub issues you will find that most people I worked with
49 > appreciated to work with me. Of course there are some bugs/PRs where I
50 > rejected a requested change but I am not sure what your point is. This
51 > is normal because not every PR is valid.
52
53 #gentoo-desktop:
54
55 [00:00:00] - {Day changed to Friday, 6 August 2021}
56 [...]
57 [13:32:33] <pinkflames[m]> soap: we went over this last week, 1. I'm not
58 making any more PRs where I do not receive the recognition I deserve and
59 2. working with Whissi is probably impossible ;(
60 [...]
61 [13:34:50] <pinkflames[m]> I'm not sure how well it got through since he
62 didn't seem to respond to my concerns but I could also tell that he
63 really has an authoritative decision making style
64
65 Timestamps so you can verify it with a third-party. This is a public
66 statement, I will not share statements by people who have confided in
67 me.
68
69 > > 1. If I say the sky is blue, you'll say it's green. If I say it's
70 > > green,
71 > > you'll say it's blue. I've had at least 5 people tell me they see
72 > > the
73 > > exact same pattern in you (and no, mgorny is not part of that set,
74 > > before you throw that point at me). You're the textbook contrarian
75 > > of
76 > > Gentoo ("Wutbürger") right now.
77 > > 2. You'll tell people they are wrong, they aren't following
78 > > protocols,
79 > > they made a mistake, but you will never follow through with actually
80 > > telling people what/why or how. By the time people ask you "why?",
81 > > you've already disappeared. Given how frequently this happens in
82 > > multiple channels, projects and at different time points,
83 > > statistically,
84 > > this can't be explained by coincidence any more. This happens
85 > > practically on a daily basis, so you're not getting the benefit of
86 > > the
87 > > doubt any more.
88 > > 3. You can't let go. The security elections disaster right now is
89 > > the
90 > > prime example (yes, it's public, just check the history of the
91 > > Security
92 > > Project). This captures you so well: it's all about **community**
93 > > and
94 > > stuff, until you lose, then you start invoking technicalities and
95 > > procedural shenanigans to justify some ludicrous kind of "co-lead"
96 > > crap.
97 > > Frankly, it's embarrassing, and you're at the centre of it. Instead
98 > > of
99 > > accepting defeat (remember, community and democracy!), you just
100 > > fudge
101 > > the results.
102 >
103 > Interesting. You don't even now my view on this but you already have
104 > an
105 > opinion and are saying that I am the culprit. I think this is called
106 > "prejudiced".
107
108 To this day, we're still waiting for your view/statement/rebuttal of the
109 points, but have yet to receive anything.
110
111 > I am pretty sure that as a ComRel member you will abstain
112 > from this case as you seem to be superior. I mean you are publicly
113 > attacking me for 10+ months, rejected any attempt from my side when I
114 > tried to speak with you to get things sorted and now you showed how
115 > biased your are...
116
117 The last message I received from you was on 10 Jul. I have sent 3
118 follow-up messages before Monday, 12 Jul (when the Bernd low hit
119 Germany). Since then, nothing. And before you invoke the Bernd argument:
120 I'm also a first responder, and while the high Rhine wasn't nearly as
121 badly affected as the middle Rhine/Eifel area in terms of floodings, I
122 understand that you might not have had the time to respond (even though
123 you pushed 19 commits to ::gentoo on 13 Jul). That said, "let me check
124 whether soap wrote something in PM" seems to have never occurred since
125 12 Jul at any point, which raises doubts as to whether this is such a
126 critical issue after all...

Replies