In https://src.fedoraproject.org/rpms/python-setuptools/pull-request/85 I got:
"diagnostics": [ { "result": "DIAGNOSTICS", "message": "Version information for libraries and programs used by rpminspect as well as storage requirements. This result is for informational and diagnostic purposes only.", "details": "rpminspect version 1.11\nzlib version 1.2.11\nlibmagic version 541\nlibclamav version 0.103.7\nlibrpm version 4.17.1\nlibxml version 20914\njson-c version 0.15\nlibcurl version 7.82.0 (OpenSSL\/3.0.5 zlib\/1.2.11 brotli\/1.0.9 libidn2\/2.3.3 libpsl\/0.21.1 (+libidn2\/2.3.2) libssh\/0.9.6\/openssl\/zlib nghttp2\/1.46.0 OpenLDAP\/2.6.2)\nlibarchive version 3.5.3 (zlib\/1.2.11 liblzma\/5.2.5 bz2lib\/1.0.8 liblz4\/1.9.3 libzstd\/1.5.2)\nlibyaml version 0.2.5\nOpenSSL version 3.0.5 5 Jul 2022\nxmlrpc-c version 1.51.0\nmsgunfmt (GNU gettext-tools) 0.21\nannocheck version 10.81.\nabidiff version 2.1.0\nkmidiff version 2.1.0\n\nSpace required to download artifacts: 0 bytes (0 B)\nSpace required to unpack artifacts: 24936283 bytes (24 MiB)\n" }, { "result": "DIAGNOSTICS", "message": "Command line arguments used to invoke rpminspect.", "details": "\/usr\/bin\/rpminspect -c \/usr\/share\/rpminspect\/fedora.yaml -Dv -k -t BAD -w \/var\/tmp\/rpminspect -a x86_64,noarch,src -o \/root\/zuul-output\/logs\/result.json -F json \/var\/tmp\/rpminspect\/python-setuptools-65.5.0-1.fc38 \/var\/tmp\/rpminspect\/python-setuptools-65.5.1-1.fc38" } ],
"changelog": [ { "result": "INFO", "waiver authorization": "Not Waivable", "message": "Inspection skipped because this build's type is not `rpm'." }
I believe this is a bug because this is an RPM package.
I've reported this to https://github.com/rpminspect/rpminspect/issues/948 but the issue was promptly closed as This appears to be a Zuul bug.
This is not blocking me or anything, but it appears to me that something is wrong. I honestly have no idea which tool is to blame, but it seems that there is some problem.
We should really start running rpminspect one way to mitigate these problems.
How far is the code to trigger rpminspect tmt test from Zuul? If that is working already in CentOS Stream, maybe it is time to unify @msrb?
Who can help with this issue?
@msrb it is, I will contact him
Yes, we want to consolidate and only run one implementation everywhere. Unfortunately things are going slow :/
I think the problem here might be that Zuul works with local mock-built RPMs, instead of Koji builds.
From rpminspect(1):
rpminspect(1)
-b TYPE, --build-type=TYPE Set the Koji build type to TYPE. By default, rpminspect will try to automatically determine the build type of the inputs. In some cases you may want to explicitly set the type if it is having trouble determining the build type. This option is most useful when using locally pro‐ vided Koji input subdirectories. Supported build types can be seen with the -l option.
So I think running rpminspect with --build-type=rpm should fix this problem.
--build-type=rpm
This is still happening.
Metadata Update from @fbo: - Issue tagged with: Zuul CI