[EPEL-devel] Re: Retiring mingw-* packages from EPEL 7

2020-02-13 Thread Stephen John Smoogen
On Thu, 13 Feb 2020 at 06:29, Richard W.M. Jones wrote: > > This has been done now. In total 107 EPEL 7 mingw-* packages > were retired, and 307 bugs closed. > Thanks Richard. -- Stephen J Smoogen. ___ epel-devel mailing list --

[EPEL-devel] Proposed official change to EPEL guidelines: modules and RHEL

2020-02-13 Thread Matthew Miller
I've been saying this for a while as if it's fact, but of course it's not actually fact until approved, so I'm puting this to the EPEL team to hopefully do so. The current guidelines * say: EPEL packages should only enhance and never disturb the Enterprise Linux distributions they were

[EPEL-devel] Re: Proposed official change to EPEL guidelines: modules and RHEL

2020-02-13 Thread Pat Riehecky
On 2/13/20 6:54 AM, Matthew Miller wrote: I've been saying this for a while as if it's fact, but of course it's not actually fact until approved, so I'm puting this to the EPEL team to hopefully do so. The current guidelines * say: EPEL packages should only enhance and never disturb the

[EPEL-devel] Re: Retiring mingw-* packages from EPEL 7

2020-02-13 Thread Richard W.M. Jones
This has been done now. In total 107 EPEL 7 mingw-* packages were retired, and 307 bugs closed. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com libguestfs lets you edit virtual

[EPEL-devel] Re: Proposed official change to EPEL guidelines: modules and RHEL

2020-02-13 Thread Troy Dawson
On Thu, Feb 13, 2020 at 4:54 AM Matthew Miller wrote: > > I've been saying this for a while as if it's fact, but of course it's not > actually fact until approved, so I'm puting this to the EPEL team to > hopefully do so. > > The current guidelines * say: > >EPEL packages should only enhance

[EPEL-devel] Haskell environment in EPEL 8

2020-02-13 Thread Mark Stopka
Hi, is anybody working on Haskell environment for EPEL 8? If not, what would be the process for me to take ownership of those packages? They were available in EPEL 6 and 7... -- Best regards / S pozdravem, BSc. Mark Stopka, BBA mobile: +420 704 373 561

[EPEL-devel] Fedora EPEL 6 updates-testing report

2020-02-13 Thread updates
The following Fedora EPEL 6 Security updates need testing: Age URL 8 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-c3bf4a8f31 php-horde-Horde-Data-2.1.5-1.el6 7 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-06ccd2148b tomcat-7.0.99-1.el6 3

[EPEL-devel] Re: How to support python 3.8 from RHEL 8.2 in EPEL?

2020-02-13 Thread Tomas Orsava
On 2/13/20 5:18 AM, Orion Poplawski wrote: On 1/30/20 8:39 AM, Miro Hrončok wrote: On 30. 01. 20 16:32, Orion Poplawski wrote: Folks -     Looks like RHEL 8.2 will have python 3.8 in addition to python 3.6.  From the 8.2 beta: Red Hat Enterprise Linux 8 for x86_64 - AppStream Beta (RPMs)

[EPEL-devel] Can we enable some "-devel" modules from CBR in the EPEL8 buildroot?

2020-02-13 Thread Miro Hrončok
Hello EPEL. It seems that we have a python38-devel module in the RHEL 8.2 Beta Code Ready Builder repository. It has only one stream but it is not a default stream due to some technical limitations. Can we please enable such stream in the EPEL8 buildroot trough some Ursa Major/Prime/...