8:27 a.m.
On Fri, Feb 05, 2021 at 12:14 Zbigniew Jędrzejewski-Szmek wrote:
[resend, since the first one seems to have gotten stuck permanently
in the moderation queue]
Hi,
I would like to make the CI pass for systemd builds. I added an rpminspect.yaml file [1]
to disable a bunch rpminspect checks, and rpminspect passes now. But I'm stuck on
rpm-install-test, which dutifully informs me that
> package systemd-247.2-3.fc34.x86_64 conflicts with
> systemd-standalone-tmpfiles < 247.2-3.fc34^ provided by
systemd-standalone-tmpfiles-247.2-3.fc34.x86_64
Duh, no surprise, I added the Conflicts myself ;)
I do NOT want to disable the test completely. I am very much interested in CI catching
the
case where packages cannot be installed or upgraded. I'd like just to either tell it
that
it should ignore systemd-standalone-tmpfiles and systemd-standalone-sysusers, or
ideally,
it would be able to guess on its own that if there are Conflicts between subpackages
from
the same built, that is intentional and should be ignored.
I looked at the docs [2, 3], but I don't see anything relevant.
[1]
https://src.fedoraproject.org/rpms/systemd/c/7e740c5252c3291d67def67d33e5...
[2] https://docs.fedoraproject.org/en-US/ci/generic_tests/#_installability
[3]
https://lists.fedoraproject.org/archives/list/ci@lists.fedoraproject.org/...
Hi Zbigniew,
The rpm-install-test job is using this role:
https://pagure.io/zuul-distro-jobs/blob/master/f/roles/repo-install-rpm/t...
It seems like a good idea to add a variable to add exclude arguments to the
repoquery command L15. Would that work for you?
Regards,
-Tristan