Re: Unresponsive maintainer for Fedora-EPEL python-django3

Hi Kamil, Firstly, apologies for dropping the ball responding to the PR. On Wed, Nov 27, 2024 at 08:30:52AM +0100, Kamil Dudka wrote: > On Wednesday, November 27, 2024 12:07:29 AM GMT+1 Michel Lind wrote: > > On Tue, Nov 26, 2024 at 12:11:27PM -0300, Marco Benatto wrote: > > > Hello all, > > > >

Re: Unresponsive maintainer for Fedora-EPEL python-django3

Hello Michel and Neal, firstly Michel thanks to work on the PR. Secondly I'm sorry to hear about the false positives. May I have your help sending some recent examples of such cases off-list please? I'm interested in investigating that so we can improve such communication avoiding false positives

Re: Unresponsive maintainer for Fedora-EPEL python-django3

On Wed, Nov 27, 2024, 02:32 Kamil Dudka wrote: > On Wednesday, November 27, 2024 12:07:29 AM GMT+1 Michel Lind wrote: > > On Tue, Nov 26, 2024 at 12:11:27PM -0300, Marco Benatto wrote: > > > Hello all, > > > > > > We recently noticed there's a couple of PRs opened to fix > > > vulnerabilities in

Re: Unresponsive maintainer for Fedora-EPEL python-django3

On Wednesday, November 27, 2024 12:07:29 AM GMT+1 Michel Lind wrote: > On Tue, Nov 26, 2024 at 12:11:27PM -0300, Marco Benatto wrote: > > Hello all, > > > > We recently noticed there's a couple of PRs opened to fix > > vulnerabilities in EPEL8 python-django3 with no response from the > > maintaine

Re: Unresponsive maintainer for Fedora-EPEL python-django3

On Tue, Nov 26, 2024 at 6:08 PM Michel Lind wrote: > > On Tue, Nov 26, 2024 at 12:11:27PM -0300, Marco Benatto wrote: > > Hello all, > > > > We recently noticed there's a couple of PRs opened to fix > > vulnerabilities in EPEL8 python-django3 with no response from the > > maintainer (CC'ed). This

Re: Unresponsive maintainer for Fedora-EPEL python-django3

On Tue, Nov 26, 2024 at 12:11:27PM -0300, Marco Benatto wrote: > Hello all, > > We recently noticed there's a couple of PRs opened to fix > vulnerabilities in EPEL8 python-django3 with no response from the > maintainer (CC'ed). This is an important update as it fixes 4 > different CVEs. > > https

Re: Unresponsive maintainer: petersen / Pandoc package not updated since June 2023: Security vulnerability, CVE-2023-35936 (medium)

Hi Jens, Apologies for resurrecting and older thread here On Thu, Feb 22, 2024 at 02:06:22PM +0800, Jens-Ulrik Petersen wrote: > (Not sure if it makes sense to post to Discourse: Haskell library reviews > are still a little bit "esoteric" since ghc uses some non-standard linking > (ie various war

Re: Unresponsive maintainer: petersen / Pandoc package not updated since June 2023: Security vulnerability, CVE-2023-35936 (medium)

Am 01.03.24 um 07:55 schrieb Jens-Ulrik Petersen: On Fri, Feb 9, 2024 at 8:05 PM Christopher Klooz > wrote: __ The package "pandoc" remains at 3.1.3 in Fedora, but pandoc is already at 3.1.11.1. Among the updates since 3.1.3, there have been two securit

Re: Unresponsive maintainer: petersen / Pandoc package not updated since June 2023: Security vulnerability, CVE-2023-35936 (medium)

On Fri, Feb 9, 2024 at 8:05 PM Christopher Klooz wrote: > The package "pandoc" remains at 3.1.3 in Fedora, but pandoc is already at > 3.1.11.1. Among the updates since 3.1.3, there have been two > security-critical (including the medium CVE-2023-35936. Security fixes are > in 3.1.4 & 3.1.6). > >

Re: Unresponsive maintainer: petersen / Pandoc package not updated since June 2023: Security vulnerability, CVE-2023-35936 (medium)

On Thu, Feb 22, 2024 at 02:06:22PM +0800, Jens-Ulrik Petersen wrote: > I realised a second open package review is > https://bugzilla.redhat.com/show_bug.cgi?id=2068718 (isocline) > - it's a newer dep for pandoc (actually hslua-repl). Done. zbyszek -- __

Re: Unresponsive maintainer: petersen / Pandoc package not updated since June 2023: Security vulnerability, CVE-2023-35936 (medium)

On Sat, Feb 17, 2024 at 11:17 AM Michel Lind wrote: > On Thu, Feb 15, 2024 at 07:53:38PM +, Christopher Klooz wrote: > > On 14/02/2024 17.35, Michel Lind wrote: > > > As a pandoc user, I'm happy to help with any reviews. Is there a list > > > where this tends to get posted, apart from devel?

Re: Unresponsive maintainer: petersen / Pandoc package not updated since June 2023: Security vulnerability, CVE-2023-35936 (medium)

On Thu, Feb 15, 2024 at 07:53:38PM +, Christopher Klooz wrote: > On 14/02/2024 17.35, Michel Lind wrote: > > As a pandoc user, I'm happy to help with any reviews. Is there a list > > where this tends to get posted, apart from devel? > > > > Thanks, > > > > Michel > > Once the package needs a

Re: Unresponsive maintainer: petersen / Pandoc package not updated since June 2023: Security vulnerability, CVE-2023-35936 (medium)

Thanks for the support. I will start to post more review requests, maybe post them on discourse too... Currently there is https://bugzilla.redhat.com/show_bug.cgi?id=2163472 (base64) which I opened 1 year ago. Jens On Fri, Feb 16, 2024 at 3:54 AM Christopher Klooz wrote: > On 14/02/2024 17.35

Re: Unresponsive maintainer: petersen / Pandoc package not updated since June 2023: Security vulnerability, CVE-2023-35936 (medium)

On 14/02/2024 17.35, Michel Lind wrote: As a pandoc user, I'm happy to help with any reviews. Is there a list where this tends to get posted, apart from devel? Thanks, Michel Once the package needs a review, the request should be found here: http://fedoraproject.org/PackageReviewStatus/ De

Re: Unresponsive maintainer: petersen / Pandoc package not updated since June 2023: Security vulnerability, CVE-2023-35936 (medium)

As a pandoc user, I'm happy to help with any reviews. Is there a list where this tends to get posted, apart from devel? Thanks, Michel On Fri, Feb 09, 2024 at 11:26:33PM +0800, Jens-Ulrik Petersen wrote: > I should also have added there's an increasing amount of technical debt > with the pandoc

Re: Unresponsive maintainer: petersen / Pandoc package not updated since June 2023: Security vulnerability, CVE-2023-35936 (medium)

Re: pandoc, we managed to build it on RISC-V thanks to the changes you merged in ghc: $ uname -a Linux vf2.home.annexia.org 5.15.0-starfive #1 SMP Sun Jun 11 07:48:39 UTC 2023 riscv64 GNU/Linux $ rpm -q pandoc pandoc-3.1.3-27.fc41.riscv64 $ pandoc --version pandoc 3.1.3 Features: -s

Re: Unresponsive maintainer: petersen / Pandoc package not updated since June 2023: Security vulnerability, CVE-2023-35936 (medium)

On 09/02/2024 16.26, Jens-Ulrik Petersen wrote: I should also have added there's an increasing amount of technical debt with the pandoc packaging - I guess I need to beg people to help with package reviews: also reminded of our packaging (review) streamlining discussion from Flock last year. Jen

Re: Unresponsive maintainer: petersen / Pandoc package not updated since June 2023: Security vulnerability, CVE-2023-35936 (medium)

Hi Jens, Thanks for the information. Unfortunately, I didn't see the bugzilla ticket. On 09/02/2024 16.23, Jens-Ulrik Petersen wrote: Hello I am here - thanks for contacting me. I was hoping to cover this as part of my F40 Change, but unfortunately I haven't gotten to it, so the Change is now

Re: Unresponsive maintainer: petersen / Pandoc package not updated since June 2023: Security vulnerability, CVE-2023-35936 (medium)

I should also have added there's an increasing amount of technical debt with the pandoc packaging - I guess I need to beg people to help with package reviews: also reminded of our packaging (review) streamlining discussion from Flock last year. Jens On Fri, 9 Feb 2024, 23:23 Jens-Ulrik Petersen,

Re: Unresponsive maintainer: petersen / Pandoc package not updated since June 2023: Security vulnerability, CVE-2023-35936 (medium)

Hello I am here - thanks for contacting me. I was hoping to cover this as part of my F40 Change, but unfortunately I haven't gotten to it, so the Change is now at risk of being deferred to F41. Nevertheless I will see what I can do about this for F40: maybe a backport can also be done for F39. N

Re: unresponsive maintainer for python-installer

On Mon, Nov 27, 2023 at 2:15 PM Kaleb Keithley wrote: > > Is someone in contact with cstratak? > > I started the non-responsive maintainer process [1], because I asked that > python-installer be branched and built for epel, or to add the EPEL > packagers SIG to the maintainers [2] on 14 Nov 2023

Re: unresponsive maintainer for python-installer

On 27. 11. 23 14:14, Kaleb Keithley wrote: Is someone in contact with cstratak? I started the non-responsive maintainer process [1], because I asked that python-installer be branched and built for epel, or to add the EPEL packagers SIG to the maintainers [2] on 14 Nov 2023 and added a NEEDINF

Re: Unresponsive maintainer: Alex Chernyakhovsky

On Wed, Jun 29, 2022 at 09:23:10PM +0200, Vitaly Zaitsev via devel wrote: > On 29/06/2022 20:58, Miro Hrončok wrote: > > No, it isn't. It's great ;) > > Why? I doubt fighting maintainers is a good thing for Fedora. Why are you assuming the added EPEL maintainers want to fight the existing maintai

Re: Unresponsive maintainer: Alex Chernyakhovsky

On Wed, 2022-06-29 at 20:09 +0200, Vitaly Zaitsev via devel wrote: > On 29/06/2022 18:47, Robbie Harwood wrote: > > I don't see how you got there.  Nowhere does it say that the > > maintainer(s) are removed - just that one is added, and made > > contact for > > EPEL bugs. > > Newly added EPEL main

Re: Unresponsive maintainer: Alex Chernyakhovsky

If you're happy with the current version 1.0.49 from rawhide being branched for epel9, then the stalled process would be a good fit. With collaborator permissions on epel* branches, you can request the epel9 branch, merge commits from rawhide to epel9, create builds, and create bodhi updates. If y

Re: Unresponsive maintainer: Alex Chernyakhovsky

Jumping in on this... I opened BZ 2095512 a few weeks ago about getting pure-ftpd for EPEL 9, with a follow-up a week ago. There's already an EPEL 8 branch, so I guess that maintainer was notified (or do all get notified)? Looking at src.fedoraproject.org, it doesn't look like any of the maintain

Re: Unresponsive maintainer: Alex Chernyakhovsky

On Wed, Jun 29, 2022 at 2:30 PM Vitaly Zaitsev via devel wrote: > > On 29/06/2022 21:06, Stephen Smoogen wrote: > > Maintainers are custodians and do not own the package. > > This becomes true with the new EPEL policy. I think it should be > revisited to follow Fedora's non-responsive maintainer p

Re: Unresponsive maintainer: Alex Chernyakhovsky

On Wed, Jun 29, 2022 at 2:09 PM Vitaly Zaitsev via devel wrote: > > On 29/06/2022 18:47, Robbie Harwood wrote: > > I don't see how you got there. Nowhere does it say that the > > maintainer(s) are removed - just that one is added, and made contact for > > EPEL bugs. > > Newly added EPEL maintaine

Re: Unresponsive maintainer: Alex Chernyakhovsky

On Wed, Jun 29, 2022 at 1:09 PM Vitaly Zaitsev via devel wrote: > > On 29/06/2022 18:47, Robbie Harwood wrote: > > I don't see how you got there. Nowhere does it say that the > > maintainer(s) are removed - just that one is added, and made contact for > > EPEL bugs. > > Newly added EPEL maintaine

Re: Unresponsive maintainer: Alex Chernyakhovsky

On 29/06/2022 21:06, Stephen Smoogen wrote: Maintainers are custodians and do not own the package. This becomes true with the new EPEL policy. I think it should be revisited to follow Fedora's non-responsive maintainer procedure with an explicit FESCo approval on a case-by-case basis. -- Si

Re: Unresponsive maintainer: Alex Chernyakhovsky

On 29/06/2022 20:58, Miro Hrončok wrote: No, it isn't. It's great ;) Why? I doubt fighting maintainers is a good thing for Fedora. -- Sincerely, Vitaly Zaitsev (vit...@easycoding.org) ___ devel mailing list -- devel@lists.fedoraproject.org To unsub

Re: Unresponsive maintainer: Alex Chernyakhovsky

Hi Robbie, On Wed, 2022-06-29 at 12:02 -0400, Robbie Harwood wrote: > In this case, because no one needinfo'd the maintainer, the EPEL > policy > can be slower (two weeks compared to the minimum ten days for > nonresponsive).  Also, a literal reading of the EPEL policy says that > the same person

Re: Unresponsive maintainer: Alex Chernyakhovsky

On Wed, 29 Jun 2022 at 14:52, Vitaly Zaitsev via devel < devel@lists.fedoraproject.org> wrote: > On 29/06/2022 20:32, Stephen Smoogen wrote: > > Yes, they can. So can a lot of other people and things in Fedora. > > Only proven-packagers in limited situations or people who have been > granted acces

Re: Unresponsive maintainer: Alex Chernyakhovsky

On 29. 06. 22 20:50, Vitaly Zaitsev via devel wrote: On 29/06/2022 20:32, Stephen Smoogen wrote: Yes, they can. So can a lot of other people and things in Fedora. Only proven-packagers in limited situations or people who have been granted access by the package owner. This isn't other distro

Re: Unresponsive maintainer: Alex Chernyakhovsky

On 29/06/2022 20:32, Stephen Smoogen wrote: Yes, they can. So can a lot of other people and things in Fedora. Only proven-packagers in limited situations or people who have been granted access by the package owner. This isn't other distros where a package maintainer is a defacto dictator of

Re: Unresponsive maintainer: Alex Chernyakhovsky

On Wed, 29 Jun 2022 at 14:10, Vitaly Zaitsev via devel < devel@lists.fedoraproject.org> wrote: > On 29/06/2022 18:47, Robbie Harwood wrote: > > I don't see how you got there. Nowhere does it say that the > > maintainer(s) are removed - just that one is added, and made contact for > > EPEL bugs. >

Re: Unresponsive maintainer: Alex Chernyakhovsky

On 29/06/2022 18:47, Robbie Harwood wrote: I don't see how you got there. Nowhere does it say that the maintainer(s) are removed - just that one is added, and made contact for EPEL bugs. Newly added EPEL maintainers can make any changes to Fedora branches. I don't like that. -- Sincerely,

Re: Unresponsive maintainer: Alex Chernyakhovsky

Vitaly Zaitsev via devel writes: > On 29/06/2022 01:18, Maxwell G via devel wrote: > >> You might also be interested in the Stalled EPEL Requests >> policy[1]. This would've allowed you to get permissions to branch the >> package for EPEL without going through the non-responsive maintainer >> pro

Re: Unresponsive maintainer: Alex Chernyakhovsky

On 29/06/2022 01:18, Maxwell G via devel wrote: You might also be interested in the Stalled EPEL Requests policy[1]. This would've allowed you to get permissions to branch the package for EPEL without going through the non-responsive maintainer process. This policy looks like a package hijack a

Re: Unresponsive maintainer: Alex Chernyakhovsky

Maxwell G via devel writes: > On Tuesday, June 28, 2022 4:30:14 PM CDT Robbie Harwood wrote: >> I have started the responsive maintainer process due to lack of contact >> through bugzilla mail. Specifically, this is about an epel9 branch, >> which has been repeatedly requested since March (inclu

Re: Unresponsive maintainer: Alex Chernyakhovsky

On Tuesday, June 28, 2022 4:30:14 PM CDT Robbie Harwood wrote: > I have started the responsive maintainer process due to lack of contact > through bugzilla mail. Specifically, this is about an epel9 branch, > which has been repeatedly requested since March (including an offer to > maintain the bra

Re: Unresponsive maintainer: Alex Chernyakhovsky

Alex Chernyakhovsky writes: > I just replied on bugzilla. No one has attempted to contact me before. Well... as a Fedora maintainer, there's an expectation that you'll read your bugzilla email from time to time :) I know stuff happens, and from your bz comment it sounds like there was some issu

Re: Unresponsive maintainer for genders package

I believe this is the upstream: https://github.com/chaos/genders It may have origins at LLNL but not entirely sure. I do know the chaos org on github hosts several HPC related applications like pdsh and powerman. There is now a EPEL8 build in testing repos. - Trey On Sun, May 2, 2021, 9:19 PM

Re: Unresponsive maintainer for genders package

Is there a current upstream for this project? https://computing.llnl.gov/linux/genders.html The page seems to be ‘not found’ as it is listed in other distro upstreams. Is this a dead project? Sent from my iPhone > On Apr 30, 2021, at 3:12 PM, treyd...@gmail.com wrote: > > Apologies, my indicat

RE: Unresponsive maintainer for genders package

Apologies, my indication of unresponsive was that I got no response when I emailed genders-maintain...@fedoraproject.org and genders-ow...@fedoraproject.org last week. Maybe that was not the best way to make contact. Thanks for adding me to the package, I'll see about getting EPEL8 builds goin

RE: Unresponsive maintainer for genders package

Trey, Not quite unresponsive, just not as interested 😉 If you want to help maintaining genders that would be helpful. I’m the only one I think managing the package right now, so getting another person would be good. I’m going to add you as admin to https://src.fedoraproject.org/rpms/genders so

Re: unresponsive maintainer: itamarjp

Hi, On Sun, Mar 29, 2020 at 10:50 PM Dominik 'Rathann' Mierzejewski wrote: > > Hi, François. > > On Sunday, 29 March 2020 at 14:59, François Cami wrote: > > Hi Itamar, > > > > I am starting the unresponsive maintainer process [0], because > > packages you maintain or co-maintain are FTBFS [1]. >

Re: unresponsive maintainer: itamarjp

Hi, François. On Sunday, 29 March 2020 at 14:59, François Cami wrote: > Hi Itamar, > > I am starting the unresponsive maintainer process [0], because > packages you maintain or co-maintain are FTBFS [1]. > Your last build action in koji dates from early December 2019 [2]. > > Unfortunately, a lo

Re: Unresponsive maintainer: jhogarth / James Hogarth (python-pyrfc3339)

PS: forgot to add the link to my bug report as required by the policy: https://bugzilla.redhat.com/show_bug.cgi?id=1774667 ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora

Re: Unresponsive maintainer: brouhaha / Eric Smith

Eric: I suspect you are still interested in participating in Fedora and I appreciate that. May I suggest that you give full "admin" co-maintainership much faster. That would enable me an others to resolve many of the bugs. :-) Felix ___ devel mailing li

Re: Unresponsive maintainer: brouhaha / Eric Smith

On 08. 11. 19 9:21, Felix Schwarz wrote: Hi, I'm trying to contact Eric Smith (FAS: brohaha). I have started the nonresponsive maintainer process because I'm trying to update the WeasyPrint package which requires updating/fixing a few other packages maintained by Eric. This is mostly about:

Re: Unresponsive maintainer: smooge Fwd: [Bug 1451148] libmaxminddb-1.3.2 is available

On Wed, 23 Oct 2019 at 12:52, Matthew Miller wrote: > > On Sun, Oct 20, 2019 at 11:46:41AM -0400, Jason Taylor wrote: > > I am interested in this package as well, I can help maintain it (fas: > > jtaylor) > > Is there an easy command-line query tool for this package, like there was > for the old d

Re: Unresponsive maintainer: smooge Fwd: [Bug 1451148] libmaxminddb-1.3.2 is available

On Sun, Oct 20, 2019 at 11:46:41AM -0400, Jason Taylor wrote: > I am interested in this package as well, I can help maintain it (fas: > jtaylor) Is there an easy command-line query tool for this package, like there was for the old db version? -- Matthew Miller Fedora Project Leader

Re: Unresponsive maintainer: smooge Fwd: [Bug 1451148] libmaxminddb-1.3.2 is available

I am interested in this package as well, I can help maintain it (fas: jtaylor) Thanks! JT On Sun, Oct 20, 2019, 10:57 Igor Gnatenko wrote: > Feel free to assign it to me and I'll try to make an update to it as > soon as possible. > > On Sun, Oct 20, 2019, 16:47 Stephen John Smoogen wrote: > >

Re: Unresponsive maintainer: smooge Fwd: [Bug 1451148] libmaxminddb-1.3.2 is available

Feel free to assign it to me and I'll try to make an update to it as soon as possible. On Sun, Oct 20, 2019, 16:47 Stephen John Smoogen wrote: > So I am declaring myself an unresponsive maintainer on the > libmaxminddb and would like someone else to take this package. > > libmaxminddb is part of

Re: Unresponsive maintainer: Hannes Frederic Sowa

No problem! Thanks for the quick resolution:-) Jirka On Fri, Sep 27, 2019 at 3:29 PM Hannes Frederic Sowa < han...@stressinduktion.org> wrote: > Hello, > > On Fri, Sep 27, 2019, at 11:21, Miro Hrončok wrote: > > On 27. 09. 19 11:07, Jiri Hladky wrote: > > > Hello Hannes, > > > > > > thanks for t

Re: Unresponsive maintainer: Hannes Frederic Sowa

Hello, On Fri, Sep 27, 2019, at 11:21, Miro Hrončok wrote: > On 27. 09. 19 11:07, Jiri Hladky wrote: > > Hello Hannes, > > > > thanks for the quick response! I'm happy to take over the datamash package. > > > > Could you please give the admin rights by going to > > https://src.fedoraproject.org/

Re: Unresponsive maintainer: Hannes Frederic Sowa

On 27. 09. 19 11:07, Jiri Hladky wrote: Hello Hannes, thanks for the quick response! I'm happy to take over the datamash package. Could you please give the admin rights by going to https://src.fedoraproject.org/rpms/datamash Settings -> Users & Groups -> Add User Or even Settings -> Give Pro

Re: Unresponsive maintainer: Hannes Frederic Sowa

Hello Hannes, thanks for the quick response! I'm happy to take over the datamash package. Could you please give the admin rights by going to https://src.fedoraproject.org/rpms/datamash Settings -> Users & Groups -> Add User Thanks a lot! Jiri On Fri, Sep 27, 2019 at 4:53 AM Hannes Frederic Sow

Re: Unresponsive maintainer: Hannes Frederic Sowa

Hello, On Thu, Sep 26, 2019, at 13:28, Jiri Hladky wrote: > I'm trying to contact Hannes Frederic Sowa, maintainer of datamash package: > > https://src.fedoraproject.org/user/stressinduktion > https://src.fedoraproject.org/rpms/datamash > > I have started the nonresponsive maintainer process due

Re: Unresponsive Maintainer: Chitlesh Goorah

Chitlesh, Just to confirm, you meant "Back in 2010 I mentioned that I could*n't* continue as a fedora developer due to time constraints.", not how you wrote it above? Geoff Marr IRC: coremodule On Wed, Sep 4, 2019 at 5:35 AM Chitlesh Goorah wrote: > Hello everyone, > > Back in 2010 I mentione

Re: Unresponsive Maintainer: Chitlesh Goorah

Hi Alain, Great to see there is some interest in the Electronics Lab Spin! Can you reach out to Chitlesh and see if he is willing to give up his spot as the maintainer of the group so that the spin can get the maintenance it needs? If I don't hear from him in a week, I'll just continue through the

Re: Unresponsive Maintainer: Chitlesh Goorah

Hi Geoffrey I am Alain, FAS: avigne, a micro-electronic engineer, mainly interested in CAD/EDA tools. I started my journey to become a Fedora packager with this spin in mind (+ introducing another PCB tool: pcb-rnd) I have been in contact with Chitlesh, and also with Kiara, who both stepped down th

Re: Unresponsive maintainer: mflobo

On Mon, May 27, 2019 at 9:56 AM Matthias Runge wrote: > On Thu, May 23, 2019 at 06:40:34PM +0200, Alfredo Moralejo Alonso wrote: > > On Wed, May 22, 2019 at 9:37 AM Didier Fabert > > wrote: > > > > > Le 21/05/2019 à 15:13, Alfredo Moralejo Alonso a écrit : > > > > Hello, > > > > > > > > I've bee

Re: Unresponsive maintainer: mflobo

On Thu, May 23, 2019 at 06:40:34PM +0200, Alfredo Moralejo Alonso wrote: > On Wed, May 22, 2019 at 9:37 AM Didier Fabert > wrote: > > > Le 21/05/2019 à 15:13, Alfredo Moralejo Alonso a écrit : > > > Hello, > > > > > > I've been trying to contact mflobo in order to get some packages updated > > >

Re: Unresponsive maintainer: mflobo

On Wed, May 22, 2019 at 9:37 AM Didier Fabert wrote: > Hi, > > It's a little off topic, but where your fedora_active_user.py script > come from ? > > I have the same problem and according to the > Policy_for_nonresponsive_package_maintainers[1], the "official" repo is > on github[2]. > > That's t

Re: Unresponsive maintainer: mflobo

Hi, It's a little off topic, but where your fedora_active_user.py script come from ? I have the same problem and according to the Policy_for_nonresponsive_package_maintainers[1], the "official" repo is on github[2]. I cannot run successfully this script with python2 or python3,and with th

Re: Unresponsive maintainer: janfrode

Am Montag, den 28.01.2019, 16:21 + schrieb Mattia Verga: > Il 1/28/19 12:53 PM, Björn 'besser82' Esser ha scritto: > > Hello, > > > > does anyone here know how to contact janfrode? I can't get him to > > answer > > on rhbz # [1], nor on his email address from FAS. > > > > > It seems he has a

Re: Unresponsive maintainer: janfrode

Il 1/28/19 12:53 PM, Björn 'besser82' Esser ha scritto: > Hello, > > does anyone here know how to contact janfrode? I can't get him to answer > on rhbz # [1], nor on his email address from FAS. > > It seems he has at least a Twitter and a LinkedIn account: https://twitter.com/janfrode https://www

Re: Unresponsive maintainer: mbaldessari

Hi Timothée, sorry am a bit swamped with work. I should be able to get to them week. cheers, Michele On Tue, Jan 15, 2019 at 09:18:39AM +0100, Timothée Floure wrote: > Hello, > > Does anyone here know how to contact mbaldessari? I can't get him to answer on > RHBZ#1640405 [0]. > > Output of `f

Re: Unresponsive Maintainer: python-ldap3

Michal gave me commit privileges and I was able to push out the changes. Happy to maintain it. In the future, even if you don't have an interest, please respond and communicate that. On Sun, Dec 16, 2018 at 1:01 AM Igor Gnatenko < ignatenkobr...@fedoraproject.org> wrote: > Sorry, I have no inter

Re: Unresponsive Maintainer: python-ldap3

Sorry, I have no interest in EPEL packages, so I didn't respond. If you would like to maintain it, I will happily add you as comaintainer. On Fri, Dec 14, 2018, 16:11 Avram Lubkin I've been trying to reach the maintainers for python-ldap3 > (ignatenkobrain, mcyprian) for the last month. I've se

Re: Unresponsive Maintainer: python-ldap3

On 14. 12. 18 16:11, Avram Lubkin wrote: I've been trying to reach the maintainers for python-ldap3 (ignatenkobrain, mcyprian) for the last month. I've sent multiple emails, submitted pull requests[1] [2], and a bug [3]. fedora_active_user.py shows occasional activity for ignatenkobrain. Does

Re: unresponsive maintainer: nss-mdns

> My FAS name is "agoode". > > > Thanks! This worked, thanks! ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: unresponsive maintainer: nss-mdns

> On Do, 08.03.18 16:51, Zbigniew Jędrzejewski-Szmek (zbyszek(a)in.waw.pl) > wrote: > > > Urks. That form doesn't support searching by real name. Adam, what's > you fedora user name? > My FAS name is "agoode". Thanks! ___ devel mailing list -- deve

Re: unresponsive maintainer: nss-mdns

On Do, 08.03.18 16:51, Zbigniew Jędrzejewski-Szmek (zbys...@in.waw.pl) wrote: > On Thu, Mar 08, 2018 at 05:45:24PM +0100, Lennart Poettering wrote: > > On Mo, 05.03.18 20:35, Adam Goode (a...@spicenitz.org) wrote: > > > > > > On Mon, Mar 05, 2018 at 06:45:35PM -, Adam Goode wrote: > > > > >

Re: unresponsive maintainer: nss-mdns

On Thu, Mar 08, 2018 at 05:45:24PM +0100, Lennart Poettering wrote: > On Mo, 05.03.18 20:35, Adam Goode (a...@spicenitz.org) wrote: > > > > On Mon, Mar 05, 2018 at 06:45:35PM -, Adam Goode wrote: > > > > > > Hi, > > > > > > Lennart has the flu, so he'll probably wont' reply immediately. > >

Re: unresponsive maintainer: nss-mdns

On Mo, 05.03.18 20:35, Adam Goode (a...@spicenitz.org) wrote: > > On Mon, Mar 05, 2018 at 06:45:35PM -, Adam Goode wrote: > > > > Hi, > > > > Lennart has the flu, so he'll probably wont' reply immediately. > > I'll ping him, but you can expect that he will want to give the > > package away.

Re: unresponsive maintainer: nss-mdns

> On Mon, Mar 05, 2018 at 06:45:35PM -, Adam Goode wrote: > > Hi, > > Lennart has the flu, so he'll probably wont' reply immediately. > I'll ping him, but you can expect that he will want to give the > package away. > Thanks, and I hope he feels better soon. Adam __

Re: unresponsive maintainer: nss-mdns

On Mon, Mar 05, 2018 at 06:45:35PM -, Adam Goode wrote: > I am following the unresponsive maintainer policy: > https://fedoraproject.org/wiki/Policy_for_nonresponsive_package_maintainers > > Bug: > https://bugzilla.redhat.com/show_bug.cgi?id=1544608 > > Does anyone know how to reach the maint

Re: unresponsive maintainer: nss-mdns

That sounds perfect! Thank you for volunteering. signature.asc Description: PGP signature ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: unresponsive maintainer: nss-mdns

> It looks like you'll be "it" if the maintainers don't respond. Do you > want to be a maintainer? Yes, I can be the maintainer. I'm currently the main upstream contributor: https://github.com/lathiat/nss-mdns/graphs/contributors ___ devel mailing list

Re: unresponsive maintainer: nss-mdns

It looks like you'll be "it" if the maintainers don't respond. Do you want to be a maintainer? signature.asc Description: PGP signature ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproj

Re: unresponsive maintainer 'jamatos'

On Friday, 9 February 2018 09.35.34 WET Zbigniew Jędrzejewski-Szmek wrote: > Hi José, > > are you still around? You activity suddenly stops around May 28th > 2017, I hope nothing serious happened. Hi, I am alive. And I have been extremely busy, specially with classes and related work in

Re: unresponsive maintainer procedure for konradm (Conrad Meyer)

On Fri, Feb 23, 2018 at 08:34:34AM -0800, Conrad Meyer wrote: > On Fri, Feb 23, 2018 at 8:16 AM, Zbigniew Jędrzejewski-Szmek > wrote: > > If anyone knows how to contact Conrad Meyer / konradm, please do so. > > > > Today one package owned by konradm, xchat-ruby, was retired as a result > > of a FE

Re: unresponsive maintainer procedure for konradm (Conrad Meyer)

On Fri, Feb 23, 2018 at 8:16 AM, Zbigniew Jędrzejewski-Szmek wrote: > If anyone knows how to contact Conrad Meyer / konradm, please do so. > > Today one package owned by konradm, xchat-ruby, was retired as a result > of a FESCo ticket [1]. The remaining ones will be orphaned in two weeks > if ther

Re: Unresponsive maintainer

2018-01-22 20:21 GMT+01:00 Matthew Miller : > > I saw him mention that he'll be at DevConf.cz, so maybe someone can > catch him there. That must have been last year. :-) Unfortunately I can't make it this time and only came last year to find new maintainers for my packages and meet with old friend

Re: Unresponsive maintainer

2018-01-22 1:23 GMT+01:00 Greg Evenden : > you might even be better to catch him over on the SUSE IRC channels, it might > be worth a shot to see if anyone in SUSE Packages those packages an are up to > date an Grab the Source RPM's from there Good idea, but this shouldn't be necessary. I'm wor

Re: Unresponsive maintainer

2018-01-22 0:38 GMT+01:00 Tao Zhao : > Hi Mamoru, > > Thanks for the information! I've pinged his gmail. Let's see how it goes. Hi Alick, sorry, I missed that mail. I have given up looking after individual packages, so make sure to use a meaningful subject if you want to catch my attention. ;-)

Re: Unresponsive maintainer

On Sun, Jan 21, 2018 at 05:38:12PM -0600, Tao Zhao wrote: > Thanks for the information! I've pinged his gmail. Let's see how it goes. I saw him mention that he'll be at DevConf.cz, so maybe someone can catch him there. -- Matthew Miller Fedora Project Leader

Re: Unresponsive maintainer

you might even be better to catch him over on the SUSE IRC channels, it might be worth a shot to see if anyone in SUSE Packages those packages an are up to date an Grab the Source RPM's from there ___ devel mailing list -- devel@lists.fedoraproject.org

Re: Unresponsive maintainer

Hi Mamoru, Thanks for the information! I've pinged his gmail. Let's see how it goes. Regards, Alick On Sat, Jan 20, 2018 at 1:57 AM, Mamoru TASAKA wrote: > Hello, > > alick9...@gmail.com wrote on 01/20/2018 12:59 PM: >> >> Hi All, >> >> As per >> https://fedoraproject.org/wiki/Policy_for_nonres

Re: Unresponsive maintainer

Hello, alick9...@gmail.com wrote on 01/20/2018 12:59 PM: Hi All, As per https://fedoraproject.org/wiki/Policy_for_nonresponsive_package_maintainers, I am posting here to see if anyone know how to contact Christoph Wickert (cwickert). The bug report is at https://bugzilla.redhat.com/show_bug

Fwd: Re: Unresponsive Maintainer: eponyme (EDB package)

ngs though I'm sometimes getting 503 errors from that site right now, so you might need to wait a while. Thanks, Michael - Original message - * From: Nicoleau Fabien To: Michael Cullen Cc: devel@lists.fedoraproject.org Subject: Re: Unresponsive Maintainer: eponyme (EDB package) Date:

Re: Unresponsive maintainer Owen Taylor (otaylor) of package metacity

On 2017-06-09 12:05, Adam Williamson wrote: On Fri, 2017-06-09 at 10:21 -0400, Owen Taylor wrote: Yes - on the livecd, the Anaconda window is managed by gnome-shell, like other applications. Note, there's one other case in which 'anaconda' runs the WM: the graphical version of initial-setup.

Re: Unresponsive maintainer Owen Taylor (otaylor) of package metacity

On Fri, 2017-06-09 at 10:21 -0400, Owen Taylor wrote: > Yes - on the livecd, the Anaconda window is managed by gnome-shell, like > other applications. Note, there's one other case in which 'anaconda' runs the WM: the graphical version of initial-setup. So the WM used by initial-setup differs on d

Re: Unresponsive maintainer Owen Taylor (otaylor) of package metacity

Yes - on the livecd, the Anaconda window is managed by gnome-shell, like other applications. Owen - Original Message - > On Thu, Jun 08, 2017 at 10:20:26PM -0400, Owen Taylor wrote: > > I've now turned over ownership of Metacity to Yaakov Selkowitz who had > > requested admin rights in

Re: Unresponsive maintainer Owen Taylor (otaylor) of package metacity

On Thu, Jun 08, 2017 at 10:20:26PM -0400, Owen Taylor wrote: > I've now turned over ownership of Metacity to Yaakov Selkowitz who had > requested admin rights in pkgdb. He may well appreciate a co-maintainer. > Note that metacity has two different roles in Fedora with somewhat > conflicting prior

Re: Unresponsive maintainer Owen Taylor (otaylor) of package metacity

I've now turned over ownership of Metacity to Yaakov Selkowitz who had requested admin rights in pkgdb. He may well appreciate a co-maintainer. Note that metacity has two different roles in Fedora with somewhat conflicting priorities: - It is used during Anaconda operation. - It is used for G

Re: Unresponsive maintainer Owen Taylor (otaylor) of package metacity

On Thu, 2017-06-08 at 20:00 -0500, Michael Catanzaro wrote: > On Thu, Jun 8, 2017 at 4:05 PM, Joachim Frieben > wrote: > > There exist several open bug reports for package metacity addressing > > the outdatedness of the version available from the build server, e.g. > > see > > > > https://

  1   2   3   >