[EPEL-devel] Re: Extras not enabled on koji?

2020-04-05 Thread Kevin Fenzi
On Sun, Apr 05, 2020 at 03:37:29PM -0500, Richard Shaw wrote:
> On Sun, Apr 5, 2020 at 9:52 AM Stephen John Smoogen 
> wrote:
> 
> > OK so swig3 seems to just be in CentOS extras and not in RHEL extras.
> >
> 
> Is this the way it should be? All the EPEL test instances are CentOS,
> right? If I run mock it uses CentOS extra. So why would the official
> builders be different?

EPEL has always built against RHEL. Unfortunately we can't simply
provide RHEL free to everyone that wants to test against it, but you can
get a free developer subscription and use that. 

> This doesn't make for a good packager experience :)

Well, not sure how to make it better. We could move to building against
CentOS, but that would be a big undertaking and some folks would like
that and some would not. 

We could perhaps advertise the developer rhel subscription more for
testing?

Open to other ideas...

kevin


signature.asc
Description: PGP signature
___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org


[EPEL-devel] Re: Putting qt5 srpm macro into epel-rpm-macros

2020-04-05 Thread Kevin Fenzi
On Fri, Apr 03, 2020 at 09:59:24AM -0700, Troy Dawson wrote:
> RHEL 8.2 will have a newer qt5 (qt5-5.12.5).
> They have also cleaned up their qt5-srpm-macros, to remove a macro for
> a package they do not support, nor plan on supporting.  I have
> verified this was their intention and they do not plan on putting it
> back.
> 
> %qt5_qtwebengine_arches %{ix86} x86_64 %{arm} aarch64 mips mipsel mips64el
> 
> The problem is that this is in all the KDE spec files for EPEL8 that
> depend on qtwebengine.  It's essentially telling them to not build on
> s390x.
> 
> I've look at all the alternatives, and putting that macro into
> epel-rpm-macros solves the problem.
> I have verified that rpmfusion doesn't build on s390x, so they will
> not be affected by this problem.
> 
> I'll be putting that in today, and letting it sit testing for the
> usual time.  If anyone has any problems, please let me know before the
> two weeks are up.

Seems fine to do to me... 

kevin


signature.asc
Description: PGP signature
___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org