[EPEL-devel] Re: What to do about old packages in epel8-playground

2019-11-05 Thread Stephen John Smoogen
On Mon, 4 Nov 2019 at 18:35, Dave Dykstra wrote: > > It seems to be worse than that. When I tried around 2 weeks ago, > building a version in epel8-playground blocked building the same version > in epel8. > https://pagure.io/releng/issue/8925 > I did similar builds earlier and didn't have

[EPEL-devel] Re: What to do about old packages in epel8-playground

2019-11-04 Thread Dave Dykstra
It seems to be worse than that. When I tried around 2 weeks ago, building a version in epel8-playground blocked building the same version in epel8. https://pagure.io/releng/issue/8925 I did similar builds earlier and didn't have the problem. I have packages.cfg that targets epel8 in the

[EPEL-devel] Re: What to do about old packages in epel8-playground

2019-11-03 Thread Orion Poplawski
On 11/3/19 12:47 PM, Kevin Fenzi wrote: On Fri, Nov 01, 2019 at 08:06:07AM -0700, Troy Dawson wrote: For KDE, I built all the packages in epel8-playground. At the time, it seemed like the right thing to do. (Whether it was or not is another discussion). I also built several packages in

[EPEL-devel] Re: What to do about old packages in epel8-playground

2019-11-03 Thread Kevin Fenzi
On Fri, Nov 01, 2019 at 08:06:07AM -0700, Troy Dawson wrote: > For KDE, I built all the packages in epel8-playground. At the time, > it seemed like the right thing to do. (Whether it was or not is > another discussion). I also built several packages in playground that > were not part of KDE,