[EPEL-devel] Re: Orphaning python-mistune on EPEL

2024-01-10 Thread Michel Lind
Hi Miro, On Wed, Jan 10, 2024 at 02:51:33PM +0100, Miro Hrončok wrote: > Hello, > > I recently took python-mistune in Fedora. > I am not interested in maintaining it in EPEL. > > It is branched for epel7, epel8 and epel9. > > @epel-packagers-sig is a collaborator so I assume somebody built

[EPEL-devel] EPEL Steering Committee Meeting Time Reschedule

2024-01-10 Thread Diego Herrera
As we discussed during last meeting, here is a poll to check if there is a timeslot that can fit more of the people that are currently interested to participate in the EPEL Steering Committee Meeting. https://whenisgood.net/EPEL_Steering_Committee_2024 What day and time would you like? Paint

[EPEL-devel] Re: Orphaning python-mistune on EPEL

2024-01-10 Thread Miro Hrončok
On 10. 01. 24 15:21, Neil Hanlon wrote: I'll take this one for epel. Thank You, Neil. Done. -- Miro Hrončok -- Phone: +420777974800 IRC: mhroncok -- ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to

[EPEL-devel] Retirement of package `godot` in EPEL7

2024-01-10 Thread Rémi Verschelde
Hi, I'm the maintainer of the `godot` [0] package in Fedora and EPEL7 (as well as the upstream maintainer). I'm following the documented procedure [1] to retire this package. I announced my intent to retire this package from EPEL7 back in October 2023 [2]. Nobody volunteered to take it over

[EPEL-devel] Re: Orphaning python-mistune on EPEL

2024-01-10 Thread Neil Hanlon
On Wed, Jan 10, 2024, 08:51 Miro Hrončok wrote: > Hello, > > I recently took python-mistune in Fedora. > I am not interested in maintaining it in EPEL. > > It is branched for epel7, epel8 and epel9. > > @epel-packagers-sig is a collaborator so I assume somebody built this in > epel9 > without

[EPEL-devel] Orphaning python-mistune on EPEL

2024-01-10 Thread Miro Hrončok
Hello, I recently took python-mistune in Fedora. I am not interested in maintaining it in EPEL. It is branched for epel7, epel8 and epel9. @epel-packagers-sig is a collaborator so I assume somebody built this in epel9 without taking responsibility. There is a low impact CVE: