Bug 2049024 - epel-8-x86_64.cfg is broken now
Summary: epel-8-x86_64.cfg is broken now
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: mock-core-configs
Version: 35
Hardware: x86_64
OS: Linux
unspecified
urgent
Target Milestone: ---
Assignee: Copr Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-02-01 11:05 UTC by Brian J. Murrell
Modified: 2022-02-02 14:32 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2022-02-01 11:13:47 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Brian J. Murrell 2022-02-01 11:05:47 UTC
Description of problem:
CentOS 8 (non-stream) is no longer available from the centos.org mirrorlist server.  The mock-core-configs are still referencing the mirrorlist URL for epel-8-x86_64.  No alternative (i.e. alma or rocky) with epel-8 is available.

Version-Release number of selected component (if applicable):
mock-core-configs-36.3-1.fc35.noarch

How reproducible:
100%

Steps to Reproduce:
1. mock -r epel-8-x86_64 <SRPM>

Actual results:
Build fails due to not being able to find 'baseos'

Expected results:
Some way of building epel-8-x86_64 packages should be available now that it's Feb. 01, 2022 and the centos.org mirrorlist server is no longer recognising releasever=8

Additional info:

Comment 1 Pavel Raiskup 2022-02-01 11:13:47 UTC
Please update to mock-core-configs 36.4:
https://bodhi.fedoraproject.org/updates/?packages=mock

Comment 2 Brian J. Murrell 2022-02-01 11:30:13 UTC
I have already done that.  The point here is that today was the "deadline" to get that update out of testing and into main.  Enough stuff breaks that is unpredictable, that we should strive to at least prevent predictable breakage.  IMHO.

Comment 3 Pavel Raiskup 2022-02-01 11:34:04 UTC
There's a plan to release updated mock-core-configs this week, so the karma in those
updates will be re-set.  Then it's up to the community if they accept the update or not,
but I don't really want to "force push" this.

Comment 4 Brian J. Murrell 2022-02-01 11:55:53 UTC
I guess what I am saying is that this was a known event.  For a long time even.  The plan should have been to do all of whatever is necessary early enough to get a graceful landing into Fedora's general repos today (at the latest), if not sooner so that people could update their CI systems ahead of the flag day.

I wonder how many CI build systems are going to break today, because they use mock on "general" Fedora, not "testing".

Comment 5 Pavel Raiskup 2022-02-01 13:30:45 UTC
I hope those who maintain CI systems closely followed the discussions on
fedora/epel devel lists.  This turned out to be a non-trivial change, even
though we planned the fix soon enough.  Fedora in general preferred to stay on
older Mock, rather than the updated one which would break rpkg/fedpkg.

But I agree.  I was informed by rpkg maintainer (cc) that the release is
being worked on.


Note You need to log in before you can comment on or make changes to this bug.