packages can be blocked from being forked in EPEL. I don't remember if that
is koji or some other higher end tool.
On 3 August 2017 at 18:09, Ken Dreyer wrote:
> On Tue, Aug 1, 2017 at 11:05 AM, Stephen John Smoogen
> wrote:
> >
> > Does the above sound
On 2017-08-03 16:35, Kevin Fenzi wrote:
> On 08/02/2017 05:51 AM, Peter Robinson wrote:
>> On Wed, Aug 2, 2017 at 5:42 AM, Yaakov Selkowitz wrote:
>>> On 2017-08-01 16:24, Stephen John Smoogen wrote:
RHEL-7.4 was released today and so the build roots for EPEL packages
On Tue, Aug 1, 2017 at 11:05 AM, Stephen John Smoogen wrote:
>
> Does the above sound reasonable ?
>
Sounds great.
It leads me to ask a question I've been wondering about for a while
w.r.t retiring Ceph from EPEL 7: How can we keep other random
contributors from re-introducing
On 08/02/2017 05:51 AM, Peter Robinson wrote:
> On Wed, Aug 2, 2017 at 5:42 AM, Yaakov Selkowitz wrote:
>> On 2017-08-01 16:24, Stephen John Smoogen wrote:
>>> RHEL-7.4 was released today and so the build roots for EPEL packages
>>> will be updated as soon as the automatic
On 08/01/2017 10:41 AM, Jason L Tibbitts III wrote:
> One of things I've invested some time towards over the years is cutting
> down on the amount of %if spaghetti needed to share spec files between
> Fedora and EPEL. Earlier in the discussion about the mass python-X ->
> python2-X move I
The following Fedora EPEL 7 Security updates need testing:
Age URL
878 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2015-1087
dokuwiki-0-0.24.20140929c.el7
641 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2015-dac7ed832f
mcollective-2.8.4-1.el7
223
The following Fedora EPEL 6 Security updates need testing:
Age URL
757 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2015-7031
python-virtualenv-12.0.7-1.el6
751 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2015-7168
rubygem-crack-0.3.2-2.el6
641
On 08/01/2017 10:05 AM, Stephen John Smoogen wrote:
> On 1 August 2017 at 12:32, Jeffrey Ollie wrote:
>
>> Building 12.1.1 for EPEL7 would be VERY bad IMNSHO. 0.80.7 _is_ seriously
>> out of date, but:
>>
>> 1) You can't upgrade directly from 0.80.7 to 12.1.1 without upgrading
On 08/01/2017 10:05 AM, Stephen John Smoogen wrote:
> I will bring this up at the meeting tomorrow, but I believe that the
> plan would be something like the following:
>
> 1. "Update" the current package with README.deprecated explaining why
> the package is being removed from the repository
On 3 August 2017 at 15:00, Kaleb S. KEITHLEY wrote:
> On 08/01/2017 01:05 PM, Stephen John Smoogen wrote:
>
>>
>>
>> On 1 August 2017 at 12:32, Jeffrey Ollie j...@ocjtech.us>> wrote:
>>
>> Building 12.1.1 for EPEL7 would be VERY bad IMNSHO. 0.80.7
On 08/01/2017 01:05 PM, Stephen John Smoogen wrote:
On 1 August 2017 at 12:32, Jeffrey Ollie > wrote:
Building 12.1.1 for EPEL7 would be VERY bad IMNSHO. 0.80.7 _is_
seriously out of date, but:
[snip]
I will bring this up at the meeting
11 matches
Mail list logo