1 |
On 05/19/2017 03:10 PM, Michał Górny wrote: |
2 |
> On Wed, 2017-05-17 at 18:38 +0200, Patrick Lauer wrote: |
3 |
>> Bonus mention: |
4 |
>> bbdc5412061adf598ed935697441a7d6b05f7614 |
5 |
>> app-admin/logstash-bin: drop old |
6 |
>> |
7 |
>> Signed-off-by: Andrew Savchenko <bircoph@g.o> |
8 |
>> |
9 |
>> That removed the versions I was using, so I better maintain the versions |
10 |
>> I use in an overlay. Well ok then. |
11 |
>> |
12 |
> |
13 |
> I'm sorry that the situation turned out badly for you. However, I would |
14 |
> like to point out that problems like this are rarely unilateral, |
15 |
> and usually involve issues on both ends. |
16 |
> |
17 |
> I'd like to ask you a very simple question: what did you do to ensure |
18 |
> that the versions you are using are not accidentally removed? |
19 |
> |
20 |
> I could have a few ideas, such as: |
21 |
> |
22 |
> a. slotting the package to indicate that multiple versions might be |
23 |
> meaningful, |
24 |
> |
25 |
> b. opening a bug requesting the old version to be kept, |
26 |
> |
27 |
> c. leaving a comment in the ebuild (unlikely to help but still), |
28 |
> |
29 |
> d. just mailing proxy-maint@ to let us know of the issue. |
30 |
|
31 |
|
32 |
I tried removing proxy-maint from metadata after multiple discussions |
33 |
failed. Extra happiness towards monsieurp "but the GH PR is over 3 days |
34 |
old, I have to commit" and gokturk "Yes I understand. I commit anyway" |
35 |
|
36 |
This has been an uphill struggle since about October, around New Year I |
37 |
stopped actively caring, and since these two commits: |
38 |
|
39 |
12c3eacda7c4d23686eaf10eab21d810cc95ea49 |
40 |
f42d6679c038c3efcc257d38547267d01823aea9 |
41 |
|
42 |
I see no way to fix this situation that doesn't involve a review board |
43 |
in front of all proxy-maint commits. Because we discussed this in IRC, |
44 |
and still ... "but is open bug" |
45 |
|
46 |
> However, as far as I'm aware none of this happened. Note that I might |
47 |
> have missed the mail, or it might have been sent before I joined -- |
48 |
> correct me if that is the case. |
49 |
|
50 |
There were multiple discussions in IRC, which the involved people |
51 |
usually forgot within about 20 minutes and then resumed doing stuff. |
52 |
|
53 |
I tried removing proxy-maint from metadata, which was reverted (sooo how |
54 |
does one *not* have constant interference?) |
55 |
|
56 |
> As Alec pointed out, it is a normal procedure in Gentoo to remove old |
57 |
> versions of software if there is no explicit indication that they need |
58 |
> to be kept. Therefore, I don't see anything wrong with the proxied |
59 |
> maintainer wishing to clean the old versions up and/or not requesting |
60 |
> your explicit permission for that. If you needed the old versions, you |
61 |
> should have made that clear. |
62 |
|
63 |
One could ask, maybe. I guess I can (mis)understand this to mean that I |
64 |
can do with packages with you in metadata what I want because ... err... |
65 |
shiny! |
66 |
|
67 |
> I should also point out that the steps you've taken (and listed in this |
68 |
> mail) are not really relevant. They make you look like a sloppy |
69 |
> maintainer, and a bad Gentoo developer at the best -- and I doubt anyone |
70 |
> would connect removing proxy-maint team with a necessity of keeping |
71 |
> an old version. |
72 |
|
73 |
The cooperation that I had with ferki was pretty good (mostly because we |
74 |
sat next to each other in the office). The contributions from Tomas were |
75 |
on average pretty ok, just needed some minor cleanups here and there. |
76 |
|
77 |
The blind "but PR is open for 3 days" commits from proxy-maint made it |
78 |
extremely hard to review what changed in a timely manner, so that I |
79 |
basically didn't want to care for this pile of stupid for the last, |
80 |
ahem, 6 months or so. Especially since whenever I wanted to review |
81 |
things some joker made some new changes which made me go "eh whut how |
82 |
you? banana banana!" so I pushed reviewing a week into the future and ... |
83 |
|
84 |
I have no idea how I could have fixed this without the QA+Comrel |
85 |
banhammer combo, which is a totally insane "fix" to a problem that |
86 |
shouldn't even exist. But I see no other options how to make people |
87 |
understand that "No means no". |
88 |
|
89 |
Is this the new normal? |