#8749 Setup EPEL8 in stg to use CentOS Devel repo
Closed: Fixed 4 years ago by kevin. Opened 4 years ago by tdawson.

Please setup the EPEL8 koji instance to add the CentOS Devel repo as an external repo.
Details about that repo can be found here.
https://lists.centos.org/pipermail/centos-devel/2020-March/036644.html


It would be great if we could have this in two weeks (2020-03-27)


Metadata Update from @smooge:
- Issue priority set to: Waiting on Assignee (was: Needs Review)
- Issue tagged with: koji, medium-gain

4 years ago

OK so CentOS Devel is only for stream. This means that libraries and such may not match RHEL-8 at all. I think if we are going to mirror use this that it will need all CentOS repos mirrored.

Why do you think they are only for stream?
There is a stream Devel, yes, but there is also a Devel repo for regular CentOS.

http://mirror.centos.org/centos/8/Devel/

OK CentOS-8 is synced down and should be available at

https://infrastructure.fedoraproject.org/repo/centos/centos-8/Devel/$arch/os/

I have not tried adding this as another external repo to stg koji as I am not sure if what is needed now.

so... I went to set this up in staging.

First wrinkle: Centos does not do s390x, we do.

I've put a empty one there in staging, but it means that anything that uses packages from Devel will have to excude s390x or it will fail to build.

It should be all set in staging, can folks test and discuss if the s390x exclude is acceptable or not and we can easily set it in prod.

Test build - The package that was missing is mobile-broadband-provider-info-devel
https://koji.stg.fedoraproject.org/koji/taskinfo?taskID=90021731

As you can see, on the non-s390x builds, it correctly installs the package and correctly builds the package.
To me this looks like success.

About the s390x, well, most of my packages that having missing dependencies are for KDE. There are already alot of desktop packages missing from s390x outside of this problem, so I already have exclude in for them. So this isn't going to affect me too much.
But, that's just me.

This should be live in prod now. :)

Let us know if there is any problems or issues...

Metadata Update from @kevin:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

4 years ago

Login to comment on this ticket.

Metadata