#12123 epel8 Koji buildroot has RHEL 8.9 packages, should be RHEL 8.10
Closed: Fixed with Explanation a month ago by kevin. Opened a month ago by churchyard.

  • Describe the issue

When I try to build epel8 packages in Koji, I get packages from RHEL 8.9 instead of RHEL 8.10 installed.

@carlwgeorge told me a job should make this right at 03:30 UTC but apparently, it didn't work:

https://pagure.io/fedora-infra/ansible/blob/main/f/roles/batcave/files/sync-rhn#_2

@kevin said on Mastodon "Ran manual sync to pick up RHEL 8.10 for epel8 builds." but apparently, it didn't work either.

When I run a CI scratchbuild from https://src.fedoraproject.org/rpms/python3-rpm/pull-request/15 I get:

rpm-libs-4.14.3-28.el8_9
No matching package to install: 'python3.12-devel'
No matching package to install: 'python3.12-setuptools'

While RHEL 8.10 mock has:

rpm-libs-4.14.3-31.el8
python3.12-devel-3.12.1-4.el8
python3.12-setuptools-68.2.2-3.el8

  • When do you need this? yesterday

  • When is this no longer needed or useful? when RHEL 8 goes EOL

  • If we cannot complete your request, what is the impact? packages in epel8 cannot be rebuilt for RHEL 8.10 changes


My first guess is that grobisplitter had problems as the data should have been synced down earlier in the day.. after that grobisplitter needs to be run to deal with the new modules. If grobisplitter died or had issues then the koji build root would be using the older data.

The problem was pretty mundane. I forgot to run the grobisplitter part... somehow I assumed it was part of the same cron, but instead it's seperate and runs at 09:10UTC.
And indeed it's run and indeed I see 8.10 in a recent build.

Sorry for the trouble, it should be all working now. If not, please re-open.

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

a month ago

Thanks, it indeed works now.

Log in to comment on this ticket.

Metadata