Re: Non-responsive maintainer: mruprich (Michal Ruprich)

2020-04-23 Thread Miro Hrončok
On 23. 04. 20 16:28, Kamil Dudka wrote: It really looks like my requests were ignored until maintainer status was called into question. Because you did not use an appropriate channel to discuss your concerns. Bugzilla is a tool to report bugs, most frequently when something does not work as

Re: Non-responsive maintainer: mruprich (Michal Ruprich)

2020-04-23 Thread Robbie Harwood
Kamil Dudka writes: > On Thursday, April 23, 2020 4:08:24 PM CEST Robbie Harwood wrote: >> That's not how this works. > > Yes and I am trying to suggest you how to make it work. > >> Even if your assertion were true (which it isn't), we have a closure >> status for that. Michal (the maintainer,

Re: Non-responsive maintainer: mruprich (Michal Ruprich)

2020-04-23 Thread Kamil Dudka
On Thursday, April 23, 2020 4:08:24 PM CEST Robbie Harwood wrote: > That's not how this works. Yes and I am trying to suggest you how to make it work. > Even if your assertion were true (which it isn't), we have a closure > status for that. Michal (the maintainer, who isn't you) even used it -

Re: Non-responsive maintainer: mruprich (Michal Ruprich)

2020-04-23 Thread Robbie Harwood
Kamil Dudka writes: > On Wednesday, April 22, 2020 7:28:36 PM CEST Robbie Harwood wrote: >> To make this as clear as I can, let's look at >> https://bugzilla.redhat.com/show_bug.cgi?id=1815163 > > The above mentioned ticket is not a bug report in the first place. That's not how this works.

Re: Non-responsive maintainer: mruprich (Michal Ruprich)

2020-04-23 Thread Kamil Dudka
On Wednesday, April 22, 2020 7:28:36 PM CEST Robbie Harwood wrote: > To make this as clear as I can, let's look at > https://bugzilla.redhat.com/show_bug.cgi?id=1815163 The above mentioned ticket is not a bug report in the first place. You just expressed your personal opinion about a package

Re: Non-responsive maintainer: mruprich (Michal Ruprich)

2020-04-22 Thread Robbie Harwood
Martin Sehnoutka writes: > Hi Robbie, > > I'm pretty sure Michal would respond if you contacted him via email. Hi Martin, you've dropped Michal from CC in your reply, but I did include Michal on my original email. In other words: this *is* contacting by email :) > Also Michal is far from

Re: Non-responsive maintainer: mruprich (Michal Ruprich)

2020-04-22 Thread Martin Sehnoutka
Good point, thanks! On 22/04/2020 10:42, Miro Hrončok wrote: On 22. 04. 20 10:21, Martin Sehnoutka wrote: Regarding the abrt reports: I can see a lot of them are for Wireshark, but given the size of Wireshark codebase and speed of its development it would require a huge effort to fix all of 

Re: Non-responsive maintainer: mruprich (Michal Ruprich)

2020-04-22 Thread Miro Hrončok
On 22. 04. 20 10:21, Martin Sehnoutka wrote: Regarding the abrt reports: I can see a lot of them are for Wireshark, but given the size of Wireshark codebase and speed of its development it would require a huge effort to fix all of them. Not related to Michal at all, more general thought: If

Re: Non-responsive maintainer: mruprich (Michal Ruprich)

2020-04-22 Thread Martin Sehnoutka
Hi Robbie, I'm pretty sure Michal would respond if you contacted him via email. Also Michal is far from being inactive on bugzilla and the fact that he has few open bugs does not prove otherwise. Regarding the abrt reports: I can see a lot of them are for Wireshark, but given the size of

Non-responsive maintainer: mruprich (Michal Ruprich)

2020-04-21 Thread Robbie Harwood
Hi, in accordance with non-responsive maintainer policy [1], does anyone know how to contact Michal Ruprich (mruprich)? Michal, if you're still interested in maintaining your packages, please respond here and also in: https://bugzilla.redhat.com/show_bug.cgi?id=1815163