[EPEL-devel] Re: Python 3.6: RHEL 7.7 vs. CentOS 7.6 EPEL7 retirement problem

On 18. 09. 19 0:55, Kevin Fenzi wrote: Now that CentOS 7.7 is out shall we retire things again? I guess we do. But I dare to touch it. It works now. -- Miro Hrončok -- Phone: +420777974800 IRC: mhroncok ___ epel-devel mailing list --

[EPEL-devel] Re: Python 3.6: RHEL 7.7 vs. CentOS 7.6 EPEL7 retirement problem

On 8/11/19 12:28 AM, Miro Hrončok wrote: > On 11. 08. 19 2:58, Stephen John Smoogen wrote: >> On Sat, 10 Aug 2019 at 17:12, Miro Hrončok > > wrote: >> >>     On 10. 08. 19 21:23, Miro Hrončok wrote: >> > While I really tried to do my best, it seems that I broke >>

[EPEL-devel] Re: Python 3.6: RHEL 7.7 vs. CentOS 7.6 EPEL7 retirement problem

On 8/13/19 11:15 AM, Miro Hrončok wrote: > On 13. 08. 19 20:08, Kevin Fenzi wrote: >> On 8/11/19 1:45 AM, Miro Hrončok wrote: >>> On 11. 08. 19 9:59, Mohan Boddu wrote: I unretired the packages and tagged the old builds, I think that should fix the buildroot and got a testing build

[EPEL-devel] Re: Python 3.6: RHEL 7.7 vs. CentOS 7.6 EPEL7 retirement problem

On 13. 08. 19 20:08, Kevin Fenzi wrote: On 8/11/19 1:45 AM, Miro Hrončok wrote: On 11. 08. 19 9:59, Mohan Boddu wrote: I unretired the packages and tagged the old builds, I think that should fix the buildroot and got a testing build working. Thanks, now. Assuming Koji sees RHEL 7.7, can we

[EPEL-devel] Re: Python 3.6: RHEL 7.7 vs. CentOS 7.6 EPEL7 retirement problem

On 8/11/19 1:45 AM, Miro Hrončok wrote: > On 11. 08. 19 9:59, Mohan Boddu wrote: >> I unretired the packages and tagged the old builds, I think that >> should fix the buildroot and got a testing build working. > > > Thanks, now. > > Assuming Koji sees RHEL 7.7, can we somehow: > >  - keep the

[EPEL-devel] Re: Python 3.6: RHEL 7.7 vs. CentOS 7.6 EPEL7 retirement problem

On Sun, 11 Aug 2019 at 03:32, Miro Hrončok wrote: > On 11. 08. 19 2:58, Stephen John Smoogen wrote: > > On Sat, 10 Aug 2019 at 17:12, Miro Hrončok > > wrote: > > > > On 10. 08. 19 21:23, Miro Hrončok wrote: > > > While I really tried to do my best, it seems

[EPEL-devel] Re: Python 3.6: RHEL 7.7 vs. CentOS 7.6 EPEL7 retirement problem

On 10. 08. 19 21:23, Miro Hrončok wrote: While I really tried to do my best, it seems that I broke CentOS by retiring python36. Should it be unretired? Or is it reasonable to say: Please wait for CentOS 7.7? https://bugzilla.redhat.com/show_bug.cgi?id=1739804 Currently I cannot even init an

[EPEL-devel] Re: Python 3.6: RHEL 7.7 vs. CentOS 7.6 EPEL7 retirement problem

On 11. 08. 19 9:59, Mohan Boddu wrote: I unretired the packages and tagged the old builds, I think that should fix the buildroot and got a testing build working. Thanks, now. Assuming Koji sees RHEL 7.7, can we somehow: - keep the packages in the repos - but make Koji prefer the RHEL ones

[EPEL-devel] Re: Python 3.6: RHEL 7.7 vs. CentOS 7.6 EPEL7 retirement problem

I unretired the packages and tagged the old builds, I think that should fix the buildroot and got a testing build working. On Sun, Aug 11, 2019 at 3:29 AM Miro Hrončok wrote: > On 11. 08. 19 2:58, Stephen John Smoogen wrote: > > On Sat, 10 Aug 2019 at 17:12, Miro Hrončok >

[EPEL-devel] Re: Python 3.6: RHEL 7.7 vs. CentOS 7.6 EPEL7 retirement problem

On 11. 08. 19 2:58, Stephen John Smoogen wrote: On Sat, 10 Aug 2019 at 17:12, Miro Hrončok > wrote: On 10. 08. 19 21:23, Miro Hrončok wrote: > While I really tried to do my best, it seems that I broke CentOS by retiring > python36. Should it be

[EPEL-devel] Re: Python 3.6: RHEL 7.7 vs. CentOS 7.6 EPEL7 retirement problem

On Sat, 10 Aug 2019 at 17:12, Miro Hrončok wrote: > On 10. 08. 19 21:23, Miro Hrončok wrote: > > While I really tried to do my best, it seems that I broke CentOS by > retiring > > python36. Should it be unretired? Or is it reasonable to say: Please > wait for > > CentOS 7.7? > > > >

[EPEL-devel] Re: Python 3.6: RHEL 7.7 vs. CentOS 7.6 EPEL7 retirement problem

Robert-André Mauchin wrote: > How long would that wait be? > RHEL7.7 is only 4 days old. Everyone running CentOS should be planning their patching cycles around the lull between a brand new RHEL Update and the CentOS build/catch-up. - bjs ___

[EPEL-devel] Re: Python 3.6: RHEL 7.7 vs. CentOS 7.6 EPEL7 retirement problem

On Saturday, 10 August 2019 21:23:55 CEST Miro Hrončok wrote: > While I really tried to do my best, it seems that I broke CentOS by retiring > python36. Should it be unretired? Or is it reasonable to say: Please wait > for CentOS 7.7? > How long would that wait be?

[EPEL-devel] Re: Python 3.6: RHEL 7.7 vs. CentOS 7.6 EPEL7 retirement problem

On 10. 08. 19 21:23, Miro Hrončok wrote: While I really tried to do my best, it seems that I broke CentOS by retiring python36. Should it be unretired? Or is it reasonable to say: Please wait for CentOS 7.7? https://bugzilla.redhat.com/show_bug.cgi?id=1739804 If any EPEL expert thinks the

[EPEL-devel] Re: Python 3.6: RHEL 7.7 vs. CentOS 7.6 EPEL7 retirement problem

Stephen John Smoogen wrote: > This was the purpose of the various branching proposals. The main issue > there are > not enough time/manpower resources to make any of the proposals work as it > needs > build system changes, a full time release manager and packagers who want to > deal with it. >

[EPEL-devel] Re: Python 3.6: RHEL 7.7 vs. CentOS 7.6 EPEL7 retirement problem

On Sat, 10 Aug 2019 at 16:18, Andrew C Aitchison wrote: > On Sat, 10 Aug 2019, Richard Grainger wrote: > > >> On 10 Aug 2019, at 20:23, Miro HronÄ ok wrote: > >> > >> While I really tried to do my best, it seems that I broke CentOS by > >> retiring python36. Should it be unretired? Or is it

[EPEL-devel] Re: Python 3.6: RHEL 7.7 vs. CentOS 7.6 EPEL7 retirement problem

> On 10 Aug 2019, at 20:23, Miro Hrončok wrote: > > While I really tried to do my best, it seems that I broke CentOS by retiring > python36. Should it be unretired? Or is it reasonable to say: Please wait for > CentOS 7.7? This is why I believe we need a “CentOS-EPEL” repo that mirrors EPEL