@fbo PTAL, would love to contribute, no idea where these things are setup :(

Hi,

Currently we run fedpkg srpm into a fedora 33 container (which need to be bumped to 34).
However no epel-rpm-macro package is available on fedora.

We have centos-8 container available (https://fedora.softwarefactory-project.io/zuul/labels) which seems to provide epel-release and epel-rpm-macros-8-26.

So we need to update our job definition to ensure centos-8 container is used as base node to run the fedpkg srpm when branch is epel8.

Let me know @mvadkert if you want to tackle this, I will provide guidance.

It seems the nodeset (https://pagure.io/fedora-zuul-jobs-config/blob/master/f/zuul.d/jobs.dhall#_138) needs to be overridden with 'centos-8-container' (which is available https://pagure.io/fedora-zuul-jobs/blob/master/f/zuul.d/nodesets.yaml#_38) only when branch is epel8 (can be done around here https://pagure.io/fedora-zuul-jobs-config/blob/master/f/zuul.d/jobs.dhall#_181 using an already existing function https://pagure.io/fedora-project-config/blob/master/f/FZCI.dhall/Branches.dhall#_77)

@fbo sorry was not around, we can try to do it if that would help.

@mvadkert yes sure any help would be welcome :)

I'm currently struggling with the bump of the default container to f34 where {{ ansible_user_dir }} do not resolve to the expected user home directory. So I'm working on removing the use of {{ ansible_user_dir }} from zuul_distro_jobs. So until this is done I won't be able to tackle this issue.

Should I re-assign to you ? Again I'll provide guidance.

Yes, assigned to me, will try to look at this this week

Currently we run fedpkg srpm into a fedora 33 container...

In that case, we just need python-srpm-macros 3.9-20.fc33 installed. We might have wrongfully assumed the SRPM system runs on EL 8, as it does on Jenkins.

This change https://pagure.io/fedora-zuul-jobs-config/pull-request/140 ensures that the python-srpm-macro is installed at the very last version available.

Let me know if that fixed the issue.

It fixes it for rpm-scratch-build but not for rpm-linter which also need up to date macros:

https://src.fedoraproject.org/rpms/python3.11/pull-request/6#comment-90463

Oh, so the rpm-linter job runs on fedora 34 containers. Our new container pipeline periodically rebuild containers but the node that run them miss a podman pull before podman run ... (there are still rough edges into that workflow ...). I've did the podman pull and now the image's python-srpm-macros package passed from python-srpm-macros-3.9-38.fc34 to python-srpm-macros-3.9-41.fc34.

I hope that will fix the issue. I've run a recheck on https://src.fedoraproject.org/rpms/python3.11/pull-request/6

Let me know.

Looks like it is fixed. However, a more permanent mechanism to ensure all rpm macro packages are up to date on CI might be needed.

@fbo sorry for not helping really :(