Build succeeded.

• linters : SUCCESS in 58s

Build succeeded.

• linters : SUCCESS in 55s

@churchyard, Hi with this commit we'll use f36 base system to run rpmlint. Instead of running rpmlint 1.11 from (f34 base system), it will use rpmlint 2.2.0. Let me know if that fine for you ?

Thanks for the heads-up. RPMlint 2 has a new configuration syntax. Change like this should probably be coordinated on the devel list. I'd also appreciate it if this was testable via Depends-On (is it?), so we can try-fail-retry to migrate to the next syntax.

Yes it can be tested speculatively by adding:

Depends-on: https://pagure.io/fedora-zuul-jobs/pull-request/157

I will prepare a mail for devel. Thanks you.

I've tried to run this command locally:

$ rpmlint --file python3.11.rpmlintrc ./python3.11-3.11.0~b4-1.fc37.src.rpm

And I got:

usage: rpmlint [-h] [-V] [-c CONFIG] [-e EXPLAIN [EXPLAIN ...]] [-r RPMLINTRC] [-v] [-p]
               [-i INSTALLED [INSTALLED ...]] [-t] [-T] [-s | -P]
               [rpmfile ...]
rpmlint: error: unrecognized arguments: --file

So assuming no other changes were made, this will probably fail that way everywhere.

I'm testing in https://src.fedoraproject.org/rpms/python3.11/pull-request/69

Yes, https://fedora.softwarefactory-project.io/zuul/build/76cb5e0d33364717850afec0548f456e

usage: rpmlint [-h] [-V] [-c CONFIG] [-e EXPLAIN [EXPLAIN ...]] [-r RPMLINTRC]
               [-v] [-p] [-i INSTALLED [INSTALLED ...]] [-t] [-T] [-s | -P]
               [rpmfile ...]
rpmlint: error: unrecognized arguments: --file

Thanks you.

I've added a Depends-on: https://pagure.io/zuul-distro-jobs/pull-request/132 on this PR to adapt the zuul-distro-jobs rpm-lint role to handle both case rpmlint 1.11 and rpmlint 2.X.

Build succeeded.

• linters : SUCCESS in 55s

As stated in https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/SVNOBWIO5NVUF46FAKXCG3TQ5V46VSE2/ it is time to merge that change. The rpm-linter job is non-voting so that won't block CI in case of wrong rpmlintrc file.

recheck

Build succeeded.

• linters : SUCCESS in 57s

Build succeeded.

• linters : SUCCESS in 54s

For some reason pagure.io set a 'threshold_reached: false' for that PR then zuul refuse to gate the change. Other open PRs get 'threshold_reached: true'. Something weird here, so I'll merge using the merge button.

:thumbsup:

Build succeeded (gate pipeline).

• linters : SUCCESS in 54s