[EPEL-devel] Re: Code Ready Builder

2019-08-26 Thread Troy Dawson
On Fri, Aug 23, 2019 at 8:21 AM Stephen John Smoogen wrote: > > On Fri, 23 Aug 2019 at 11:03, Paul Howarth wrote: > > > > The EL-8 non-default repo Code Ready Builder is primarily targeted at > > developers, but it looks to me like it's going to be a required repo > > for a lot of EPEL-8 users, p

[EPEL-devel] Re: itstool missing in aarch64 and s390x

2019-08-26 Thread Troy Dawson
On Sun, Aug 25, 2019 at 2:05 PM Stephen John Smoogen wrote: > > On Sun, 25 Aug 2019 at 08:31, Mukundan Ragavan wrote: > > > > The package "itstool" seems to be missing in some architectures (s390x > > and aarch64) although it should be provided by RHEL server rpms. It > > appears to be available

[EPEL-devel] Re: Rules for shadowing RHEL packages with EPEL modules

2019-08-26 Thread Troy Dawson
On Fri, Aug 23, 2019 at 5:27 AM Stephen John Smoogen wrote: > > The following answers are just my opinions and not policy. > > On Fri, 23 Aug 2019 at 06:52, Petr Pisar wrote: > > > > Case: RHEL delivers an M module with no default stream, there is no S > > stream. > > Can I add a new S stream in

[EPEL-devel] Re: Modularity Policy Discussion for EPEL 8.1

2019-08-26 Thread Petr Pisar
On Fri, Aug 23, 2019 at 01:56:09PM -0400, Stephen Gallagher wrote: > So, I see the following options for how to handle default streams in RHEL 8 > > Option 1: We disallow assigning default streams at all within EPEL 8. > This will protect us against a future change where RHEL wants to set a > defa