On Fri, Apr 3, 2020 at 3:21 PM Troy Dawson wrote:
>
> EPEL Issue #101 [1] has pointed out that our current policy for
> stalled EPEL requests is fairly in-efficient and can cause some long
> delays.
>
> What do people think the process should be?
>
> Here is an example:
> * A packager opens a
The following Fedora EPEL 7 Security updates need testing:
Age URL
604 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-3c9292b62d
condor-8.6.11-1.el7
346 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-c499781e80
python-gnupg-0.4.4-1.el7
344
The following Fedora EPEL 6 Security updates need testing:
Age URL
7 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-b1a5eb3ef5
librabbitmq-0.5.2-2.el6
4 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-22ba261c73
drupal7-ckeditor-1.19-1.el6
4
The following Fedora EPEL 8 Security updates need testing:
Age URL
33 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-02f03affd4
ansible-2.9.6-1.el8
4 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-83cd17b92f
nrpe-4.0.2-2.el8
3
My blunder, it was looking for sextractor++
apologies for the noise
On Fri, Apr 10, 2020 at 9:20 AM Scott Talbert wrote:
> I see:
>
>
> https://dl.fedoraproject.org/pub/epel/7/x86_64/Packages/s/sourcextractor++-0.10-1.el7.x86_64.rpm
>
> On Fri, 10 Apr 2020, Tony Schreiner wrote:
>
> >
> > This
I see:
https://dl.fedoraproject.org/pub/epel/7/x86_64/Packages/s/sourcextractor++-0.10-1.el7.x86_64.rpm
On Fri, 10 Apr 2020, Tony Schreiner wrote:
This announcement is 11 days ago now, but I still don't see the package with
yum, nor on https://dl.fedoraproject.org/pub/epel/7/x86_64/Packages/
This announcement is 11 days ago now, but I still don't see the package
with yum, nor on https://dl.fedoraproject.org/pub/epel/7/x86_64/Packages/
-- Forwarded message -
From:
Date: Tue, Mar 31, 2020 at 10:57 PM
Subject: Fedora EPEL 7 Update: sourcextractor++-0.10-1.el7
To:
On 10. 04. 20 14:58, Felix Schwarz wrote:
I guess I'll start with the other packages to ensure I don't miss any
blockers. May I add you to the cc of the review request to ensure this will be
handled correctly?
Sure. Also, at this point, feel free not to package the python3_other
subpackage.
Am 10.04.20 um 13:40 schrieb Miro Hrončok:
> On 10. 04. 20 12:05, Felix Schwarz wrote:
>> What is the best way to get a Python 3 version for EPEL 7?
>
> Do a new package review request for an epel7 only package called
> python3-configobj that looks like:
Thank you for your advice - even though
On 10. 04. 20 12:05, Felix Schwarz wrote:
What is the best way to get a Python 3 version for EPEL 7?
Do a new package review request for an epel7 only package called
python3-configobj that looks like:
https://src.fedoraproject.org/rpms/python3-six/blob/epel7/f/python3-six.spec
When
Hi,
I want to move certbot from Python 2 -> Python 3 in EPEL 7. As you might
imagine this means getting Python3 packages of all required libraries. Most of
them are pretty straight forward (I hope) - just build the Python 3 version
also on EPEL 7.
However there is python-configobj which is
11 matches
Mail list logo
