Non-responsive maintainer check for avesh

2020-04-26 Thread Emmanuel Seyman
Hello, Anybody knows how to contact Avesh Agarwal (fas:avesh) ? I have a bug filed in Bugzilla that has not seen any action for 6+ months now. BZ: https://bugzilla.redhat.com/show_bug.cgi?id=1748553 Emmanuel ___ devel mailing list --

Non-responsive maintainer check for trondham

2020-04-26 Thread Igor Gnatenko
Hello, Anybody knows how to contact Trond? I have sent him an email last week, but no response (neither in bugzilla). BZ: https://bugzilla.redhat.com/show_bug.cgi?id=1827995 ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send

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,

[Bug 1806619] Non-responsive maintainer check for normunds

2020-04-23 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1806619 Scott Talbert changed: What|Removed |Added Status|NEW |CLOSED Resolution|---

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: laxathom (Xavier Lamien)

2020-04-23 Thread Vít Ondruch
Hi Xavier, Since this thread has your attention, I'd like to take over rubygem-json, if you don't mind. Vít Dne 22. 04. 20 v 21:03 Xavier Lamien napsal(a): > Oh hi, > > Looks like your email get lost in the pile if you tried to reach me > personally or my bugzilla's filter is too efficient

Re: Non-responsive maintainer: laxathom (Xavier Lamien)

2020-04-22 Thread Breno Brand Fernandes
Thanks for answering Xavier. I am checking with Vascom why I can't see the libgdiplus-devel in EPEL 8. - Breno On Wed, 22 Apr 2020 at 15:04, Xavier Lamien wrote: > Oh hi, > > Looks like your email get lost in the pile if you tried to reach me > personally or my bugzilla's filter is too

Re: Non-responsive maintainer: laxathom (Xavier Lamien)

2020-04-22 Thread Breno Brand Fernandes
Hi Vascom, I don't see the -devel package available. Why is that? On Wed, 22 Apr 2020 at 15:07, Vascom wrote: > I already built it. > > But you can update to 6.0.5 :) > > ср, 22 апр. 2020 г. в 22:04, Xavier Lamien : > > > > Oh hi, > > > > Looks like your email get lost in the pile if you tried

Re: Non-responsive maintainer: laxathom (Xavier Lamien)

2020-04-22 Thread Xavier Lamien
Thanks Vasiliy, much appreciated. On Wed, Apr 22, 2020, 9:07 PM Vascom wrote: > I already built it. > > But you can update to 6.0.5 :) > > ср, 22 апр. 2020 г. в 22:04, Xavier Lamien : > > > > Oh hi, > > > > Looks like your email get lost in the pile if you tried to reach me > personally or my

Re: Non-responsive maintainer: laxathom (Xavier Lamien)

2020-04-22 Thread Vascom
I already built it. But you can update to 6.0.5 :) ср, 22 апр. 2020 г. в 22:04, Xavier Lamien : > > Oh hi, > > Looks like your email get lost in the pile if you tried to reach me > personally or my bugzilla's filter is too efficient I'd say. > > Any way, I'll have a look at your ticket asap. >

Re: Non-responsive maintainer: laxathom (Xavier Lamien)

2020-04-22 Thread Xavier Lamien
Oh hi, Looks like your email get lost in the pile if you tried to reach me personally or my bugzilla's filter is too efficient I'd say. Any way, I'll have a look at your ticket asap. Also, I'm more than welcome to get co-maintainer on this package so feel free to request access since you're

Non-responsive maintainer: laxathom (Xavier Lamien)

2020-04-22 Thread Breno Brand Fernandes
Hi, I've been trying to get in contact with Xavier Lamien since Sep 2019 [1]. The package libgdiplus is particularly important to have mono built in EPEL 8. I am following the policy for non-responsive package maintainers [2]. In 7 days if I don't get any answers I will be filling a ticket to

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
of Wireshark codebase and speed of its development it would require a huge effort to fix all of them. So please contact him via email, I'm pretty sure you will find solutions for your bugs. Regards, Martin On 21/04/2020 23:32, Robbie Harwood wrote: Hi, in accordance with non-responsive maintainer

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 https

non-responsive maintainer: elyscape (Eli Young)

2020-04-10 Thread Felix Schwarz
Hi, following the policy for non-responsive package maintainers [0], I'm asking here if anybody knows how to contact elyscape (Eli Young). Eli, if you're still interested in maintaining your packages, please respond. Open bugs: - python-digitalocean-1.15.0 is available

Re: Non-responsive maintainer: kyrofa

2020-04-03 Thread Michel Alexandre Salim
8. > > > > I've opened a bug asking for either an EPEL 8 branch for squashfuse, > > or to be added as an admin or committer, on March 2nd: > > > > https://bugzilla.redhat.com/show_bug.cgi?id=1809433 > > > > emailed him via the squashfuse

Non-responsive maintainer: ndim

2020-04-03 Thread Michel Alexandre Salim
=1806773 emailed him via the terminus-fonts-owner alias on March 27, and just opened a non-responsive maintainer bug today: https://bugzilla.redhat.com/show_bug.cgi?id=1820751 There are open bugs dating to January for terminus-fonts, and one bug from 2015 asking for an EPEL7 branch for avrdude

Non-responsive maintainer: kyrofa

2020-04-03 Thread Michel Alexandre Salim
://bugzilla.redhat.com/show_bug.cgi?id=1809433 emailed him via the squashfuse-owner alias on March 27, and just opened a non-responsive maintainer bug today: https://bugzilla.redhat.com/show_bug.cgi?id=1820749 He seems to only maintain squashfuse, and it has bugs dating back to April 4 2018

Non-responsive maintainer gilboa

2020-03-28 Thread Artem Tim
https://bugzilla.redhat.com/show_bug.cgi?id=1818461 CC: gilb...@gmail.com ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct:

Re: EPEL8 - unable to build package due to non-responsive maintainer of dependencies

2020-03-26 Thread Kevin Fenzi
On Thu, Mar 26, 2020 at 11:29:36AM -0400, Stephen John Smoogen wrote: > On Thu, 26 Mar 2020 at 11:28, Stephen John Smoogen wrote: > > > > > > > On Thu, 26 Mar 2020 at 07:00, Ján ONDREJ wrote: > > > >> Hello, > >> > >> I am maintainer of TurboGears packages in Fedora. After release of RHEL8, >

Re: EPEL8 - unable to build package due to non-responsive maintainer of dependencies

2020-03-26 Thread Stephen John Smoogen
On Thu, 26 Mar 2020 at 11:28, Stephen John Smoogen wrote: > > > On Thu, 26 Mar 2020 at 07:00, Ján ONDREJ wrote: > >> Hello, >> >> I am maintainer of TurboGears packages in Fedora. After release of RHEL8, >> I am trying to build it for EPEL. But there are some dependencies, which >> are not

Re: EPEL8 - unable to build package due to non-responsive maintainer of dependencies

2020-03-26 Thread Stephen John Smoogen
On Thu, 26 Mar 2020 at 07:00, Ján ONDREJ wrote: > Hello, > > I am maintainer of TurboGears packages in Fedora. After release of RHEL8, > I am trying to build it for EPEL. But there are some dependencies, which > are not satisfied yet. What complicates my work is, that the unresponsible >

EPEL8 - unable to build package due to non-responsive maintainer of dependencies

2020-03-26 Thread Ján ONDREJ
Hello, I am maintainer of TurboGears packages in Fedora. After release of RHEL8, I am trying to build it for EPEL. But there are some dependencies, which are not satisfied yet. What complicates my work is, that the unresponsible maintainer is a SIG, currently infra-sig. I have filled some

Re: Non-responsive maintainer: pocock

2020-03-23 Thread Jared K. Smith
On Sun, Mar 22, 2020 at 8:10 PM Daniel Pocock wrote: > As mentioned in the RTC thread, here is the review request: > > https://bugzilla.redhat.com/show_bug.cgi?id=1815936 > I've started the review, but I'm running into some issues in compiling the software, as shown in the bug referenced above.

Re: Non-responsive maintainer: pocock

2020-03-22 Thread Daniel Pocock
On 20/03/2020 00:08, Neal Gompa wrote: > On Thu, Mar 19, 2020 at 6:42 PM Daniel Pocock wrote: >> I had added Dakota as developer (commit?) and when I looked tonight, I >> notice he had vanished. I've added him now as admin. Is there any way >> to see how he vanished? Does he need to

Re: Non-responsive maintainer: pwalter

2020-03-22 Thread Charalampos Stratakis
- Original Message - > From: "Pete Walter" > To: "Neal Gompa" > Cc: "Development discussions related to Fedora" > , "Pete Walter" > > Sent: Saturday, March 21, 2020 4:44:43 PM > Subject: Re: Non-responsive maintainer: pwal

Re: Non-responsive maintainer: pwalter

2020-03-21 Thread Miro Hrončok
On 21. 03. 20 16:41, Pete Walter wrote: Thanks for asking nicely (instead of demanding like Neal Gompa did ...). Neal actually asked you nicely several times, including the original Buzgilla. It seemed like you were not there, so he rightfully initiated the non-responsive policy. Please

Re: Non-responsive maintainer: pwalter

2020-03-21 Thread Pete Walter
21.03.2020, 10:15, "Neal Gompa" : > On Sat, Mar 21, 2020 at 6:02 AM Pete Walter wrote: >>  For months!? This is the first email I get from you. Just for the record, I >> am around, but have 0 interest in EPEL 8 as of the moment. > > In that case, I'd be happy to take on co-maintainership (admin)

Re: Non-responsive maintainer: pwalter

2020-03-21 Thread Pete Walter
Sure, I've bumped the access level and please go ahead. Thanks for asking nicely (instead of demanding like Neal Gompa did ...). Pete 21.03.2020, 15:20, "Pierre-Yves Chibon" : > On Sat, Mar 21, 2020 at 10:02:18AM +, Pete Walter wrote: >>  For months!? This is the first email I get from

Re: Non-responsive maintainer: pwalter

2020-03-21 Thread Pierre-Yves Chibon
On Sat, Mar 21, 2020 at 10:02:18AM +, Pete Walter wrote: > For months!? This is the first email I get from you. Just for the record, I > am around, but have 0 interest in EPEL 8 as of the moment. Hi Pete, The infra-sig group has already commit access to pygit2, however, to request a new

Re: Non-responsive maintainer: pwalter

2020-03-21 Thread Neal Gompa
On Sat, Mar 21, 2020 at 6:02 AM Pete Walter wrote: > > For months!? This is the first email I get from you. > That's really surprising. I had CC'd you on each email requesting for assistance on getting pagure's dependencies into EPEL 8 from December through now, and I filed the bug asking for an

Re: Non-responsive maintainer: pwalter

2020-03-21 Thread Neal Gompa
On Sat, Mar 21, 2020 at 6:02 AM Pete Walter wrote: > > For months!? This is the first email I get from you. Just for the record, I > am around, but have 0 interest in EPEL 8 as of the moment. > In that case, I'd be happy to take on co-maintainership (admin) or even take over the package

Re: Non-responsive maintainer: pwalter

2020-03-21 Thread Pete Walter
w.r.t. python-pygit2[0]. Unfortunately, he hasn't been responding to > my emails[1][2][3] (he was CC'd to all of those) or the bug I filed > requesting pygit2 for EPEL 8[4]. > > I've also filed the requisite non-responsive maintainer check bug: > https://bugzilla.redhat.com/show_bug.cgi?id=18

Re: Non-responsive maintainer: pwalter

2020-03-21 Thread Igor Gnatenko
] (he was CC'd to all of those) or the bug I filed > > requesting pygit2 for EPEL 8[4]. > > > > I've also filed the requisite non-responsive maintainer check bug: > > https://bugzilla.redhat.com/show_bug.cgi?id=1815734 > > > > Does anyone know how to get in touch

Re: Non-responsive maintainer: pwalter

2020-03-21 Thread Fabio Valentini
gt; requesting pygit2 for EPEL 8[4]. > > I've also filed the requisite non-responsive maintainer check bug: > https://bugzilla.redhat.com/show_bug.cgi?id=1815734 > > Does anyone know how to get in touch with him? You could try to resubmit Igor's libgit2-0.99 update to f31+f32,

Non-responsive maintainer: pwalter

2020-03-21 Thread Neal Gompa
Hello all, I've been trying to get in touch with Pete Walter for a few months now w.r.t. python-pygit2[0]. Unfortunately, he hasn't been responding to my emails[1][2][3] (he was CC'd to all of those) or the bug I filed requesting pygit2 for EPEL 8[4]. I've also filed the requisite non-responsive

Re: Non-responsive maintainer: pocock

2020-03-19 Thread Neal Gompa
On Thu, Mar 19, 2020 at 6:42 PM Daniel Pocock wrote: > > > > On 15/03/2020 13:32, Neal Gompa wrote: > > On Fri, Mar 6, 2020 at 2:06 PM Dakota Williams > > wrote: > >> > >> On 3/6/20 1:21 PM, Daniel Pocock wrote: > >>> > >>> > >>> On 05/03/2020 21:26, Julian Sikorski wrote: > >>> > I would

Re: Non-responsive maintainer: pocock

2020-03-19 Thread Daniel Pocock
On 15/03/2020 13:32, Neal Gompa wrote: > On Fri, Mar 6, 2020 at 2:06 PM Dakota Williams > wrote: >> >> On 3/6/20 1:21 PM, Daniel Pocock wrote: >>> >>> >>> On 05/03/2020 21:26, Julian Sikorski wrote: >>> I would like to take this opportunity to remind about the PR that I have prepared

[Bug 1806619] Non-responsive maintainer check for normunds

2020-03-19 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1806619 Fedora Admin XMLRPC Client changed: What|Removed |Added Assignee|fedora...@rule.lv |s...@techie.net ---

Re: Non-responsive maintainer: pocock

2020-03-15 Thread Neal Gompa
On Fri, Mar 6, 2020 at 2:06 PM Dakota Williams wrote: > > On 3/6/20 1:21 PM, Daniel Pocock wrote: > > > > > > On 05/03/2020 21:26, Julian Sikorski wrote: > > > >> I would like to take this opportunity to remind about the PR that I have > >> prepared - let us not duplicate the work: > >>

Re: Non-responsive maintainer: pocock

2020-03-07 Thread Neal Gompa
On Sat, Mar 7, 2020 at 11:47 AM Daniel Pocock wrote: > > On 07/03/2020 10:32, Julian Sikorski wrote: > > > In any case, Fedora is a more bleeding edge distro than Debian/Ubuntu > > (First one of the foundations), so I am not sure how realistic it is to > > be waiting for Debian/Ubuntu to include

Re: Non-responsive maintainer: pocock

2020-03-07 Thread Daniel Pocock
On 07/03/2020 10:32, Julian Sikorski wrote: > W dniu 06.03.2020 o 19:21, Daniel Pocock pisze: >> >> >> On 05/03/2020 21:26, Julian Sikorski wrote: >> >>> I would like to take this opportunity to remind about the PR that I have >>> prepared - let us not duplicate the work: >>>

Re: Non-responsive maintainer: pocock

2020-03-07 Thread Neal Gompa
On Sat, Mar 7, 2020 at 9:02 AM Julian Sikorski wrote: > > W dniu 07.03.2020 o 13:53, Neal Gompa pisze: > > On Fri, Mar 6, 2020 at 1:21 PM Daniel Pocock wrote: > >> > >> > >> If upstreams are using travis-ci, we are testing against version 1.12.2 > >> from Debian/Ubuntu and may not be aware of

Re: Non-responsive maintainer: pocock

2020-03-07 Thread Julian Sikorski
W dniu 07.03.2020 o 13:53, Neal Gompa pisze: On Fri, Mar 6, 2020 at 1:21 PM Daniel Pocock wrote: If upstreams are using travis-ci, we are testing against version 1.12.2 from Debian/Ubuntu and may not be aware of issues in asio 1.14.0. Even if you patch for the issue, it may be completely

Re: Non-responsive maintainer: pocock

2020-03-07 Thread Neal Gompa
On Fri, Mar 6, 2020 at 1:21 PM Daniel Pocock wrote: > > > If upstreams are using travis-ci, we are testing against version 1.12.2 > from Debian/Ubuntu and may not be aware of issues in asio 1.14.0. Even > if you patch for the issue, it may be completely untested upstream. > That is why it is so

Re: Non-responsive maintainer: pocock

2020-03-07 Thread Julian Sikorski
W dniu 06.03.2020 o 19:21, Daniel Pocock pisze: On 05/03/2020 21:26, Julian Sikorski wrote: I would like to take this opportunity to remind about the PR that I have prepared - let us not duplicate the work: https://src.fedoraproject.org/rpms/asio/pull-request/1 I have rebuilt all asio's

Re: Non-responsive maintainer: pocock

2020-03-06 Thread Dakota Williams via devel
On 3/6/20 1:21 PM, Daniel Pocock wrote: On 05/03/2020 21:26, Julian Sikorski wrote: I would like to take this opportunity to remind about the PR that I have prepared - let us not duplicate the work: https://src.fedoraproject.org/rpms/asio/pull-request/1 I have rebuilt all asio's dependencies

Re: Non-responsive maintainer: pocock

2020-03-06 Thread Daniel Pocock
On 05/03/2020 21:26, Julian Sikorski wrote: > I would like to take this opportunity to remind about the PR that I have > prepared - let us not duplicate the work: > https://src.fedoraproject.org/rpms/asio/pull-request/1 > I have rebuilt all asio's dependencies and only encountered issues with >

Re: Non-responsive maintainer: pocock

2020-03-05 Thread Julian Sikorski
W dniu 05.03.2020 o 21:01, Daniel Pocock pisze: > > > On 03/03/2020 23:23, Dakota Williams wrote: >> On 3/3/20 4:10 AM, Daniel Pocock wrote: > >>> >>> But based on what you say, I'm happy to give access to Dakota and I'd >>> also like to know if anybody else can help with the reSIProcate >>>

Re: Non-responsive maintainer: pocock

2020-03-05 Thread Daniel Pocock
On 03/03/2020 23:23, Dakota Williams wrote: > On 3/3/20 4:10 AM, Daniel Pocock wrote: >> >> But based on what you say, I'm happy to give access to Dakota and I'd >> also like to know if anybody else can help with the reSIProcate >> packages.  There is a new release in the pipeline and if

Re: Non-responsive maintainer: pocock

2020-03-03 Thread Daniel Pocock
n the thread AND putting some prefix on the subject. Here is what I see: From: devel-ow...@lists.fedoraproject.org Subject: Re: Non-responsive maintainer: pocock >> >> - the last message sent from the pocock.pro address was on 19 August, it >> was delivered to

Re: Non-responsive maintainer: pocock

2020-03-03 Thread Dakota Williams via devel
On 3/3/20 4:10 AM, Daniel Pocock wrote: On 28/02/2020 10:00, Ankur Sinha wrote: On Thu, Feb 27, 2020 17:07:21 -0500, Dakota Williams via devel wrote: On 2/26/20 6:59 PM, Daniel Pocock wrote: Would you like help? I'd be willing to be a co-maintainer to make the branch. Yes, I would

Re: Non-responsive maintainer: pocock

2020-03-03 Thread Radka Janekova
On Fri, Feb 28, 2020 at 1:39 PM Daniel Pocock wrote: > > On 28/02/2020 11:21, Radka Janekova wrote: > > Please excuse me going completely offtopic here - for some reason I'm > > getting this thread addressed directly to me. If someone's adding me as > > bcc please don't, I have nothing to do

Re: Non-responsive maintainer: pocock

2020-03-03 Thread Kevin Fenzi
On Tue, Mar 03, 2020 at 05:52:10PM +0100, Daniel Pocock wrote: > > Thanks for doing that > > Here are some observations: > > - the original email was sent to my pocock.com.au address and so my mail > client replied to all mails using that address, I didn't notice until > now. That address is

Re: Non-responsive maintainer: pocock

2020-03-03 Thread Daniel Pocock
On 03/03/2020 17:35, Neal Gompa wrote: > On Tue, Mar 3, 2020 at 4:10 AM Daniel Pocock wrote: >> >> >> >> On 28/02/2020 10:00, Ankur Sinha wrote: >>> On Thu, Feb 27, 2020 17:07:21 -0500, Dakota Williams via devel wrote: On 2/26/20 6:59 PM, Daniel Pocock wrote: >> >> Would you

Re: Non-responsive maintainer: pocock

2020-03-03 Thread Neal Gompa
On Tue, Mar 3, 2020 at 4:10 AM Daniel Pocock wrote: > > > > On 28/02/2020 10:00, Ankur Sinha wrote: > > On Thu, Feb 27, 2020 17:07:21 -0500, Dakota Williams via devel wrote: > >> On 2/26/20 6:59 PM, Daniel Pocock wrote: > >> > > Would you like help? I'd be willing to be a co-maintainer

Re: Non-Responsive Maintainer: bsjones

2020-03-03 Thread Felix Schwarz
ontribute. Unfortunately sometimes maintainers "disappear" but the FESCo process is a good one to ensure new maintainers can help out. In general I feel as long as you are working in good faith no one will blame you even if there was a premature "non-responsive maintainer" bug.

Re: Non-responsive maintainer: pocock

2020-03-02 Thread Neal Gompa
On Fri, Feb 28, 2020 at 1:23 PM Julian Sikorski wrote: > > Hi Daniel, > > I would like to add to Ankur's point: while I understand that many of us are > doing Fedora work voluntarily and the expectations should be set accordingly, > I believe we should be open to accept help when we realise

Non-Responsive Maintainer: bsjones

2020-03-02 Thread Erich Eickmeyer
Hello all, I have had zero success in contacting Brendan Jones per the non-responsive maintainer checks I filed in Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1806161 https://bugzilla.redhat.com/show_bug.cgi?id=1806162 Additionally, I attempted a pull request on fedora-jam

Re: Non-responsive maintainer: pocock

2020-02-28 Thread Julian Sikorski
Hi Daniel, I would like to add to Ankur's point: while I understand that many of us are doing Fedora work voluntarily and the expectations should be set accordingly, I believe we should be open to accept help when we realise that we cannot realistically commit enough time to the project. In

Re: Non-responsive maintainer: pocock

2020-02-28 Thread Radka Janekova
Please excuse me going completely offtopic here - for some reason I'm getting this thread addressed directly to me. If someone's adding me as bcc please don't, I have nothing to do with this. Thanks, Radka -- *Radka Janeková (she/her)* .NET Core QE Lead, Red Hat

Re: Non-responsive maintainer: pocock

2020-02-28 Thread Ankur Sinha
On Thu, Feb 27, 2020 17:07:21 -0500, Dakota Williams via devel wrote: > On 2/26/20 6:59 PM, Daniel Pocock wrote: > > > > > > > Would you like help? I'd be willing to be a co-maintainer to make the > > > branch. > > > > Yes, I would welcome help with these packages > > > > But there is also an

Re: Non-responsive maintainer: pocock

2020-02-27 Thread Dakota Williams via devel
On 2/26/20 6:59 PM, Daniel Pocock wrote: On 26/02/2020 22:56, Dakota Williams wrote: On 2/24/20 5:57 PM, Daniel Pocock wrote: On 24/02/2020 20:47, Dakota Williams wrote: Does anyone know how to contact maintainer pocock? https://bugzilla.redhat.com/show_bug.cgi?id=1806708

Re: Non-responsive maintainer: pocock

2020-02-26 Thread Dakota Williams via devel
On 2/24/20 5:57 PM, Daniel Pocock wrote: On 24/02/2020 20:47, Dakota Williams wrote: Does anyone know how to contact maintainer pocock? https://bugzilla.redhat.com/show_bug.cgi?id=1806708 https://bugzilla.redhat.com/show_bug.cgi?id=1790674 Like most developers, I have a backlog of things

Re: Non-responsive maintainer: pocock

2020-02-24 Thread Artur Iwicki
On FSF Europe's mailing lists, DP's using the "daniel at pocock dot pro" address. I guess you could try messaging him using that address. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to

Non-responsive maintainer: pocock

2020-02-24 Thread Dakota Williams via devel
Does anyone know how to contact maintainer pocock? https://bugzilla.redhat.com/show_bug.cgi?id=1806708 https://bugzilla.redhat.com/show_bug.cgi?id=1790674 Thanks, Dakota ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an

Non-responsive maintainer: normunds

2020-02-24 Thread Scott Talbert
Does anyone know how to contact maintainer normunds? https://bugzilla.redhat.com/show_bug.cgi?id=1806619 https://bugzilla.redhat.com/show_bug.cgi?id=1797039 Thanks, Scott ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an

[Bug 1806619] New: Non-responsive maintainer check for normunds

2020-02-24 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1806619 Bug ID: 1806619 Summary: Non-responsive maintainer check for normunds Product: Fedora Version: rawhide Hardware: All OS: Linux Status: NEW Component

Re: Non-responsive maintainer check for libffi maintainer

2020-02-24 Thread Jeff Law
On Mon, 2020-02-24 at 13:02 +, devel- requ...@lists.fedoraproject.org wrote: > > Date: Mon, 24 Feb 2020 12:10:49 +0100 > From: Miro Hrončok > Subject: Re: Non-responsive maintainer check for libffi maintainer > To: Anthony Green > Cc: Development discussions

Re: Non-responsive maintainer check for libffi maintainer

2020-02-24 Thread Christopher Engelhard
On 2/24/2020 1:46 AM, Anthony Green wrote: >I would be very happy if somebody could pick up the libffi packaging > responsibility from me. I'd be happy to adopt libffi, but given that I am a VERY new packager and this is a pretty core package, I think it would be best if someone with a bit

Re: Non-responsive maintainer check for libffi maintainer

2020-02-24 Thread Miro Hrončok
On 24. 02. 20 1:46, Anthony Green wrote: I would be very happy if somebody could pick up the libffi packaging responsibility from me. Suggestion: Try announcing on devel list that you are seeking co-maintainers (from a separate thread). If that doesn't help, orphan the package and see who

Re: Non-responsive maintainer: devrim (gdal, proj, geos)

2020-02-24 Thread Sandro Mani
On 12.02.20 10:23, Sandro Mani wrote: Hi Devrim Please keep me as co-maintainer. I'm already maintaining these packages in the upstream repository (https://yum.PostgreSQL.org) with more options there, and I'd like to keep things in sync as much as possible. Thanks for your reply. I read

Re: Non-responsive maintainer check for libffi maintainer

2020-02-23 Thread Anthony Green
Miro, I would be very happy if somebody could pick up the libffi packaging responsibility from me. For what it's worth, I'm about to make _another_ ABI-changing upstream release (to .so.8). An opaque object type (trampoline) is changing size in order to support Intel's Control-Flow

Non-responsive maintainer check for libffi maintainer

2020-02-23 Thread Miro Hrončok
Hello Anthony, I am trying to determine if you are still interested in maintaining your Fedora packages, namely libffi. I cannot see any activity in Koji since 2017, but there were some commits in https://src.fedoraproject.org/rpms/libffi/commits/master cca 8 months ago, which is confusing.

Non-responsive maintainer: Brendan Jones (bsjones)

2020-02-22 Thread Erich Eickmeyer
I have filed the following non-responsive maintainer checks for bsjones regarding packages fedora-jam-kde-theme and fedoar-jam-backgrounds: https://bugzilla.redhat.com/show_bug.cgi?id=1806161 https://bugzilla.redhat.com/show_bug.cgi?id=1806162 Here is the fedora-active-user output: Last login

Re: Non-Responsive Maintainer Check for jsmith

2020-02-12 Thread Alex Scheel
Thanks! Non-responsive maintainer check canceled from my perspective. - Original Message - > From: "Jared Smith" > To: "Alex Scheel" > Cc: "Development discussions related to Fedora" > > Sent: Wednesday, February 12, 2020 1:14:11 AM &

Re: Non-responsive maintainer: devrim (gdal, proj, geos)

2020-02-12 Thread Sandro Mani
Hi Devrim Please keep me as co-maintainer. I'm already maintaining these packages in the upstream repository (https://yum.PostgreSQL.org) with more options there, and I'd like to keep things in sync as much as possible. Thanks for your reply. I read this as you being ok if I proceed with the

Re: Non-responsive maintainer: devrim (gdal, proj, geos)

2020-02-12 Thread Tom Hughes
On 12/02/2020 07:29, Devrim Gündüz wrote: Hi Sandro (and Tom), On Wed, 2020-02-12 at 00:01 +, Tom Hughes wrote: I've attempted to contact devrim directly 2019-11-27 offering to take care of updating these packages, but received no reply. My recent PR to update gdal [2] also received no

Re: Non-Responsive Maintainer Check for jsmith

2020-02-11 Thread Jared Smith
On Tue, Feb 11, 2020 at 4:01 PM Alex Scheel wrote: > I'm initiating the non-responsive maintainer policy for jsmith. > Sorry for the slow reply -- I've been busy lately finishing up graduate school, and I was on vacation last week. I will attempt to respond to your bugzilla request as q

Re: Non-responsive maintainer: devrim (gdal, proj, geos)

2020-02-11 Thread Tom Hughes
On 11/02/2020 23:49, Sandro Mani wrote: The gdal, proj and geos packages in Fedora are outdated (plus, recent QGIS refuses to build against proj 6.2.0). The latest activity by devrim related to these packages are: - 2019-11-06: EL8 only gdal-3.0.2 update, which failed to build - 2019-09-02:

Non-responsive maintainer: devrim (gdal, proj, geos)

2020-02-11 Thread Sandro Mani
Hi I'm following the non-responsive maintainer process to ask whether anyone knows how to contact devrim. Per policy, I've filed a bug for gdal at [1]. The gdal, proj and geos packages in Fedora are outdated (plus, recent QGIS refuses to build against proj 6.2.0). The latest activity

Non-Responsive Maintainer Check for jsmith

2020-02-11 Thread Alex Scheel
I'm initiating the non-responsive maintainer policy for jsmith. Per: https://docs.fedoraproject.org/en-US/fesco/Policy_for_nonresponsive_package_maintainers/ Week -1: Mail to jsmith (cc: devel@). Sent 7 February 2020. Subject: nodejs-babel-runtime - orphan? https

[Bug 1795179] Non-responsive maintainer check for ddick

2020-02-10 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1795179 Fedora Admin XMLRPC Client changed: What|Removed |Added Assignee|dd...@cpan.org |xav...@bachelot.org ---

Non-responsive maintainer: David Dick (ddick)

2020-01-27 Thread Xavier Bachelot
2016-03-03. He seems to be still active on CPAN though: https://metacpan.org/author/DDICK Anyone knows how to contact him ? Here's the non-responsive maintainer bug : https://bugzilla.redhat.com/show_bug.cgi?id=1795179 The following bugs are assigned to him: https://bugzilla.redhat.com

[Bug 1795179] New: Non-responsive maintainer check for ddick

2020-01-27 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1795179 Bug ID: 1795179 Summary: Non-responsive maintainer check for ddick Product: Fedora Version: rawhide Hardware: All OS: Linux Status: NEW Component: perl

Re: Non-responsive maintainer: bashton

2019-12-18 Thread Robbie Harwood
James Paul Turner writes: > Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1785011 > > This bug is part of the non-responsive maintainer procedure for > btashton, following > https://docs.fedoraproject.org/en-US/fesco/Policy_for_nonresponsive_package_maintainers/ >

Non-responsive maintainer: btashton

2019-12-18 Thread James Paul Turner
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1785011 This bug is part of the non-responsive maintainer procedure for btashton, following https://docs.fedoraproject.org/en-US/fesco/Policy_for_nonresponsive_package_maintainers/ . Both of your packages are FTBFS in rawhide, including

Re: Non-responsive maintainer tchaikov

2019-12-18 Thread Vitaly Zaitsev via devel
On 18.12.2019 09:07, kefu chai wrote: > Vitaly, sorry for the latency. thanks for your help. already added you > as an admin of fmt project. Thanks. Build completed: https://koji.fedoraproject.org/koji/buildinfo?buildID=1423531 -- Sincerely, Vitaly Zaitsev (vit...@easycoding.org)

Re: Non-responsive maintainer tchaikov

2019-12-18 Thread kefu chai
On Wed, Dec 18, 2019 at 3:38 PM Vitaly Zaitsev via devel wrote: > > On 18.12.2019 01:43, Brad Hubbard wrote: > > I spoke to the maintainer. He said he'll take a look this weekend. His > > workload is truly enormous and mind boggling so please be patient. > > Please ask him to add me as

Re: Non-responsive maintainer tchaikov

2019-12-17 Thread Vitaly Zaitsev via devel
On 18.12.2019 01:43, Brad Hubbard wrote: > I spoke to the maintainer. He said he'll take a look this weekend. His > workload is truly enormous and mind boggling so please be patient. Please ask him to add me as co-maintainer to fmt package. I can help him with packaging. My FAS username: xvitaly

Re: Non-responsive maintainer tchaikov

2019-12-17 Thread Vitaly Zaitsev via devel
On 17.12.2019 20:18, Ken Dreyer wrote: > Is there a particular Fedora bug that you need Kefu to address? https://bugzilla.redhat.com/show_bug.cgi?id=1747062 Package fmt need to be updated to version 6.x at least in Rawhide. Currently it locked 3 of my packages. If he has no free time, he can

Re: Non-responsive maintainer tchaikov

2019-12-17 Thread Brad Hubbard
I spoke to the maintainer. He said he'll take a look this weekend. His workload is truly enormous and mind boggling so please be patient. On Wed, Dec 18, 2019 at 5:26 AM Robbie Harwood wrote: > > Ken Dreyer writes: > > > I work on a team at Red Hat with Kefu. He is very active with upstream > >

Re: Non-responsive maintainer tchaikov

2019-12-17 Thread Robbie Harwood
Ken Dreyer writes: > I work on a team at Red Hat with Kefu. He is very active with upstream > Ceph, though I have not watched his Fedora activity or lack thereof. > > Is there a particular Fedora bug that you need Kefu to address? This is probably about

Re: Non-responsive maintainer tchaikov

2019-12-17 Thread Richard Shaw
I only see one day of activity on src.fedoraproject.org... https://src.fedoraproject.org/user/tchaikov Thanks, Richard ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora

<    1   2   3   4   5   6   7   8   9   >