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: Fwd: Unresponsive maintainer: petersen / Pandoc package not updated since June 2023: Security vulnerability, CVE-2023-35936 (medium)

Thanks! :) On 09/02/2024 13.18, Luna Jernberg wrote: CCed his work email in case he looks there -- Forwarded message - Från: Christopher Klooz Date: fre 9 feb. 2024 kl 13:05 Subject: Unresponsive maintainer: petersen / Pandoc package not updated since June 2023: Security

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

CCed his work email in case he looks there -- Forwarded message - Från: Christopher Klooz Date: fre 9 feb. 2024 kl 13:05 Subject: Unresponsive maintainer: petersen / Pandoc package not updated since June 2023: Security vulnerability, CVE-2023-35936 (medium) To: Development

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

I cannot reach the maintainer petersen (see mail below): 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). The actu

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

unresponsive maintainer for python-installer

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 NEEDINFO on 16 Nov. Even after allowing for holidays,

Unresponsive maintainer for python-prometheus_client

Hello, does anyone know how to contact *jkaluza*? I’m trying to get python-prometheus_client updated[1], but its maintainer jkaluza is unresponsive. Thus, I have opened the corresponding non-responsive maintainer issue[2]. I’d be okay with taking maintainership of the package if needed. Kin

Re: asciiDoc: Package outdated; unresponsive maintainer?

Thanks for the information. I filed a ticket, so everyone should get an email, including Fab by his private mail address: https://bugzilla.redhat.com/show_bug.cgi?id=2171184 On 2/18/23 14:06, Ben Beasley wrote: Fabian Affolter has been consistently active in Fedora. At the same time, he maint

Re: asciiDoc: Package outdated; unresponsive maintainer?

Fabian Affolter has been consistently active in Fedora. At the same time, he maintains a huge number of packages that he does not seem to have time to keep up to date. My experience is that he usually does not—but occasionally does—respond to efforts to contact him, including Bugzilla, PR’s, and

asciiDoc: Package outdated; unresponsive maintainer?

Hi all, Does anyone know about the maintainer "Fab"? I have tried to contact him through asciidoc-maintain...@fedoraproject.org on 29th January and through f...@fedoraproject.org on 11th February, but did not received an answer from either. asciiDoc has not been updated for two years with 1

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 interested in helping with the long term maintenance of the package, to include getting it updated to the latest version (perhaps before building it for epel9 so that package can start on the latest version), then it's worth considering the unresponsive maintainer process.

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

EPEL growth. We're not going to do that. The origin of this policy is that the full unresponsive maintainer process is overkill for getting a package added to EPEL. Maintainer1 shouldn't have to suggest that all of maintainer2's packages be orphaned or assigned to themselves in or

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: Stalled EPEL Request Policy (was Unresponsive maintainer: Alex Chernyakhovsky)

On Wednesday, June 29, 2022 1:24:07 PM CDT Maxwell G via devel wrote: > On Wednesday, June 29, 2022 1:09:07 PM CDT Vitaly Zaitsev via devel wrote: > > Newly added EPEL maintainers can make any changes to Fedora branches. I > > don't like that. > > I'm a bit confused. You say this sounds like a "pa

Re: Stalled EPEL Request Policy (was Unresponsive maintainer: Alex Chernyakhovsky)

On 29/06/2022 21:23, zebo...@gmail.com wrote: What do you mean it is not possible? Isn't the new "collaborator" role exactly for this? Yes, didn't know about it. My bad. Thanks for the info. Collaborator: A user or a group with this level of access can do everything what a user/group with ti

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: Stalled EPEL Request Policy (was Unresponsive maintainer: Alex Chernyakhovsky)

On 6/29/22 8:45 PM, Vitaly Zaitsev via devel wrote: On 29/06/2022 20:24, Maxwell G wrote: > I'm a bit confused. You say this sounds like a "package hijack attempt," but > then you also say you don't like that it only allows access to epel* branches. It is not possible to restrict access to onl

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: Stalled EPEL Request Policy (was Unresponsive maintainer: Alex Chernyakhovsky)

On 29/06/2022 20:24, Maxwell G wrote: I'm a bit confused. You say this sounds like a "package hijack attempt," but then you also say you don't like that it only allows access to epel* branches. It is not possible to restrict access to only selected branches. EPEL maintainers can commit to Fedo

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. >

Stalled EPEL Request Policy (was Unresponsive maintainer: Alex Chernyakhovsky)

On Wednesday, June 29, 2022 1:09:07 PM CDT 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

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

Unresponsive maintainer: Alex Chernyakhovsky

Hi Alex + Fedora, I'm trying to contact Alex Chernyakhovsky, the maintainer of mosh. Does anyone know how to contact them? 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 reques

Unresponsive maintainer for timeshift

Hello. Is someone in contact with *srakitnican*? I started the n*on-responsive maintainer* process [0], because timeshift doesn't work since Fedora Linux 35 was released. In the meanwhile upstream released various new versions, and bugs were reported [1]. Someone created a COPR repository with

Unresponsive maintainer for python-flask-whooshee

Hello This is more of an FYI, and me doing this for the first time, and trying to follow the instructions closely, rather than looking for a way to contact the unresponsive maintainer. BZ ticket: https://bugzilla.redhat.com/show_bug.cgi?id=2042681 We already talked with rkuska privately before

Unresponsive maintainer for pdsh package

I'd like to report what I think is an unresponsive maintainer for the pdsh package. I opened a bugzilla to get an EPEL8 branch created: https://bugzilla.redhat.com/show_bug.cgi?id=1960006 and have gotten no response from that or from direct emails to maintainers. I would be happy to bec

Unresponsive Maintainer request for package tbb (Thread Building Blocks)

project regarding some unintentional ABI breakage in this version. I made a request to be added to the mainteers list for TBB on May 04, but have not heard back from the 'main admin' maintainer on that. request. I have filed an unresponsive maintainer ticket as outlined in the non-

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

maintainer for genders package Check twice before you click! This email originated from outside PNNL. I'd like to report what I think is an unresponsive maintainer for the genders package. Per https://docs.fedoraproject.org/en-US/fesco/Policy_for_nonresponsive_package_maintainers/<https

Unresponsive maintainer for genders package

I'd like to report what I think is an unresponsive maintainer for the genders package. Per https://docs.fedoraproject.org/en-US/fesco/Policy_for_nonresponsive_package_maintainers/ I filed this bug: https://bugzilla.redhat.com/show_bug.cgi?id=1955798 There do not appear to be any other bugs

Unresponsive maintainer: pkajaba

Hello, does anyone know how to contact pkajaba, who is main admin of java-comment-preprocessor in fedora ? https://bugzilla.redhat.com/show_bug.cgi?id=1890573 Thanks, Ondrej ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send a

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 > > pac

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]. >

unresponsive maintainer: itamarjp

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 lot of your packages are scheduled to be orphaned [3] soon. I will follow the

Unresponsive maintainer: moezroy / Moez Roy (davfs2)

Hi, following the policy for non-responsive package maintainers [0], I'm asking here if anybody knows how to contact moezroy (Moez Roy). Moez, if you're still interested in maintaining your packages, please respond. There several open bugs without response [1], including bug 1762083 [2] where a

Unresponsive maintainer: anujmore / Anuj More

Hi Anuj, I am starting unresponsive maintainer process [0], because I am trying to contact you in attempt to fix [1] after years. Your last action I am aware of is granting permissions to rubygem-lumberjack [2], but that is already almost two years and unfortunately, neither your other packages

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

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

Hi, following the policy for non-responsive package maintainers [0], I'm asking here if anybody knows how to contact jhogarth (James Hogarth). James, if you're still interested in maintaining your packages, please respond. python-pyrfc3339 did not get an update to 1.1. Release monitoring filed

Unresponsive maintainer: brouhaha / Eric Smith

Hi, (repost as I forgot to cc Eric) 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: - python-c

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:

Unresponsive maintainer: brouhaha / Eric Smith

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: - python-cairocffi - python-pyphen Bugzil

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

hn 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 the replacement of the GeopIP packages to work >> with their new database. I took the pa

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. > > lib

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

So I am declaring myself an unresponsive maintainer on the libmaxminddb and would like someone else to take this package. libmaxminddb is part of the replacement of the GeopIP packages to work with their new database. I took the package because it was orphaned and at the time I figured I could

Re: liblognorm unresponsive maintainer

Jiří Vymazal wrote on 2019/10/16 22:05: I have opened BZ ticket [1] for unresponsive maintainer mdarade (CC'd). Does anyone know how to contact him? (outside of his email, already tried that some time before) Thanks [1]: https://bugzilla.redhat.com/show_bug.cgi?id=1762227 By the way

liblognorm unresponsive maintainer

I have opened BZ ticket [1] for unresponsive maintainer mdarade (CC'd). Does anyone know how to contact him? (outside of his email, already tried that some time before) Thanks [1]: https://bugzilla.redhat.com/show_bug.cgi?id=1762227 -- Jiri Vymazal Software Engineer, Platform Sec

Unresponsive Maintainer: bpereto

Hi fellow Fedorans, I'm trying to contact Benjamin Pereto (FAS: bpereto), maintainer of borgbackup and borgmatic. https://src.fedoraproject.org/user/bpereto https://src.fedoraproject.org/rpms/borgmatic I have started the non-responsive maintainer process as borgmatic has not seen an upd

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

Unresponsive maintainer: Hannes Frederic Sowa

Hi Fedora, 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 to lack of contact through bugzilla mail: https://bugzilla

Re: Possibly unresponsive maintainer: vakwetu

On 13. 09. 19 20:10, Dinesh Prasanth Moluguwan Krishnamoorthy wrote: I will request Ade to transfer the "Main Admin" access to one of the members of the Dogtag team. Thank you. -- Miro Hrončok -- Phone: +420777974800 IRC: mhroncok ___ devel mailing l

Re: Possibly unresponsive maintainer: vakwetu

On Fri, 2019-09-13 at 18:51 +0200, Miro Hrončok wrote: > On 13. 09. 19 16:33, Dinesh Prasanth Moluguwan Krishnamoorthy wrote: > > Currently, the members of the dogtag team own this package. > > Not correct, it is still owned by vakwetu. Let me take back my words and rephrase. Dogtag team maintain

Re: Possibly unresponsive maintainer: vakwetu

On 13. 09. 19 16:33, Dinesh Prasanth Moluguwan Krishnamoorthy wrote: Currently, the members of the dogtag team own this package. Not correct, it is still owned by vakwetu. -- Miro Hrončok -- Phone: +420777974800 IRC: mhroncok ___ devel mailing list -

Re: Possibly unresponsive maintainer: vakwetu

Hello everyone, Ade recently added me as an admin to the project. I had added resteasy to the Stewardship SIG a while ago by following the (legacy) instructions on the SIG webpage. The package was then removed since it was little too much for the SIG. A lot of deps were brought in by resteasy that

Re: Possibly unresponsive maintainer: vakwetu

On Fri, Sep 13, 2019 at 3:57 PM Ade Lee wrote: > > Hi all, > > I transferred ownership a little while back to the resteasy package to > the SIG via Dinesh, copied above. Hi Ade, This is not accurate. You are still listed as the main admin for resteasy: https://src.fedoraproject.org/rpms/resteasy

Re: Possibly unresponsive maintainer: vakwetu

On 13. 09. 19 12:05, Fabio Valentini wrote: On Tue, Jul 9, 2019 at 8:17 PM Fabio Valentini wrote: On Tue, Jul 9, 2019 at 7:51 PM Dinesh Prasanth Moluguwan Krishnamoorthy wrote: Hello everyone, As Rob had responded earlier, he is away for few weeks. A while back, I spoke to him in person abou

Re: Possibly unresponsive maintainer: vakwetu

On Tue, Jul 9, 2019 at 8:17 PM Fabio Valentini wrote: > > On Tue, Jul 9, 2019 at 7:51 PM Dinesh Prasanth Moluguwan > Krishnamoorthy wrote: > > > > Hello everyone, > > > > As Rob had responded earlier, he is away for few weeks. A while back, I > > spoke to him in person about handing over the REST

Re: Unresponsive Maintainer: Chitlesh Goorah

ing to contact Chitlesh Goorah [0], as he is the maintainer of the > Fedora Electronics Lab Spin [1]. The spin desperately needs some love and > maintenance. Does anyone know how to contact him? I have reached out to him > three times in total, once in 2016, and again twice in 2019 and haven&

Re: Unresponsive Maintainer: Chitlesh Goorah

ue through the unresponsive maintainer process to get access. I would like to first start by removing some packages that just don't work anymore, and add a few that could greatly benefit this spin. I would welcome all of your help to get this done as I am a software engineer by day, hardware hack

Re: Unresponsive Maintainer: Chitlesh Goorah

eds some love and > maintenance. Does anyone know how to contact him? I have reached out to him > three times in total, once in 2016, and again twice in 2019 and haven't > heard back. I have started the unresponsive maintainer process, here is a > link to the Bugzilla bug [2]. After a w

Unresponsive Maintainer: Chitlesh Goorah

2019 and haven't heard back. I have started the unresponsive maintainer process, here is a link to the Bugzilla bug [2]. After a week of this mail being on the list, I will open a FESCo ticket. Thanks, Geoff Marr IRC: coremodule [0] https://fedoraproject.org/wiki/User:Chitlesh [1]

Re: Possibly unresponsive maintainer: vakwetu

On 09. 07. 19 16:16, Rob Crittenden wrote: Miro Hrončok wrote: On Tue, Jul 9, 2019 at 3:26 PM Rob Crittenden wrote: He's on PTO for a few weeks. I wonder how valid this remark is when he has not responded in years. I can't speak to his previous work as a maintainer that but I have persona

Re: Possibly unresponsive maintainer: vakwetu

On Tue, Jul 9, 2019 at 7:51 PM Dinesh Prasanth Moluguwan Krishnamoorthy wrote: > > Hello everyone, > > As Rob had responded earlier, he is away for few weeks. A while back, I > spoke to him in person about handing over the RESTeasy packages to the > Fedora SIG. He had agreed to it. Once he is back

Re: Possibly unresponsive maintainer: vakwetu

Hello everyone, As Rob had responded earlier, he is away for few weeks. A while back, I spoke to him in person about handing over the RESTeasy packages to the Fedora SIG. He had agreed to it. Once he is back, I will remind him to transfer those packages to the SIG. PS: Dogtag PKI depends on those

Re: Possibly unresponsive maintainer: vakwetu

Miro Hrončok wrote: On Tue, Jul 9, 2019 at 3:26 PM Rob Crittenden wrote: He's on PTO for a few weeks. I wonder how valid this remark is when he has not responded in years. I can't speak to his previous work as a maintainer that but I have personal knowledge that he is away. I'll otherwise

  1   2   3   4   5   >