[Fedocal] Reminder meeting : Fedora Infrastructure

2020-07-29 Thread smooge
Dear all,

You are kindly invited to the meeting:
   Fedora Infrastructure on 2020-07-30 from 15:00:00 to 16:00:00 UTC
   At fedora-meetin...@irc.freenode.net

The meeting will be about:
Weekly Fedora Infrastructure meeting. See infrastructure list for agenda a day 
before.


Source: https://apps.fedoraproject.org/calendar/meeting/9675/

___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-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/infrastructure@lists.fedoraproject.org


Re: s390x for EPEL

2020-07-29 Thread Stephen John Smoogen
On Wed, 29 Jul 2020 at 08:03, Pavel Raiskup  wrote:
>
> On Tuesday, July 28, 2020 3:17:56 PM CEST Stephen John Smoogen wrote:
> > On Mon, 27 Jul 2020 at 15:46, Kevin Fenzi  wrote:
> > >
> > > On Mon, Jul 27, 2020 at 04:45:58PM +0200, Miroslav Suchý wrote:
> > > > What is using Koji to build EPEL builds for s390x.
> > >
> > > We are using 2 LPARS on a z13 mainframe in a Red Hat lab in Westford, MA.
> > >
> > > > We want to enable s390x in Copr. It is without problem for Fedora, but 
> > > > we cannot do that for EPEL, because there is no
> > >
> > > Can you explain how you plan to do Fedora s390x builds? Emulation?
> > >
> > > > CentOS for s390x. Do we have entitlements for RHEL I can use? Or we 
> > > > have some local repo? Something completely different?
> > >
> > > We have local repo synced from RHN with our Fedora Org.
> > >
> > > I don't think we can give external access to that repo.
> > >
> > > It might also be weird to have just one arch of something be against
> > > RHEL instead of Centos. Is there no Centos port in progress?
> > >
> >
> > CentOS does not have access to an s390 to do a port.
>
> You mean no access to IBM _hardware_, right?
>

My understanding is limited to what CentOS has access to and probably
wrong. Yes you could try building it all through emulation.. I do not
know how well it would work.
-- 
Stephen J Smoogen.
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-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/infrastructure@lists.fedoraproject.org


Re: s390x for EPEL

2020-07-29 Thread Pavel Raiskup
On Tuesday, July 28, 2020 3:17:56 PM CEST Stephen John Smoogen wrote:
> On Mon, 27 Jul 2020 at 15:46, Kevin Fenzi  wrote:
> >
> > On Mon, Jul 27, 2020 at 04:45:58PM +0200, Miroslav Suchý wrote:
> > > What is using Koji to build EPEL builds for s390x.
> >
> > We are using 2 LPARS on a z13 mainframe in a Red Hat lab in Westford, MA.
> >
> > > We want to enable s390x in Copr. It is without problem for Fedora, but we 
> > > cannot do that for EPEL, because there is no
> >
> > Can you explain how you plan to do Fedora s390x builds? Emulation?
> >
> > > CentOS for s390x. Do we have entitlements for RHEL I can use? Or we have 
> > > some local repo? Something completely different?
> >
> > We have local repo synced from RHN with our Fedora Org.
> >
> > I don't think we can give external access to that repo.
> >
> > It might also be weird to have just one arch of something be against
> > RHEL instead of Centos. Is there no Centos port in progress?
> >
> 
> CentOS does not have access to an s390 to do a port.

You mean no access to IBM _hardware_, right?

Pavel

> 
> 
> > kevin
> > ___
> > infrastructure mailing list -- infrastructure@lists.fedoraproject.org
> > To unsubscribe send an email to infrastructure-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/infrastructure@lists.fedoraproject.org
> 
> 
> 
> -- 
> Stephen J Smoogen.
> ___
> infrastructure mailing list -- infrastructure@lists.fedoraproject.org
> To unsubscribe send an email to infrastructure-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/infrastructure@lists.fedoraproject.org
> 



___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-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/infrastructure@lists.fedoraproject.org