-
Notifications
You must be signed in to change notification settings - Fork 394
apt-devel to BuildRequires; apt-libs to Requires #1932
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
@candrews Thank for opening this PR. Can you help us understand the goal of this change? AFAIU you want our CI to build OpenSCAP with dpkginfo and sql57 probe so that it's tested in the GitHub actions. Is my understanding correct? That has 2 problems: 1. It doesn't build on CentOS. 2. there are no tests for the dpkginfo probe, so it would only test whether it builds correctly. |
Yes. My other motivation is to provide a better reference for packagers to use. For example, right now, Fedora's openscap package is missing the sql57 and dpkginfo dependencies, presumably because the packager used the
Why not? Is that perhaps something that could be fixed?
That's better than nothing :) |
Thanks for the explanation!
Actually it was the opposite, we created the upstream openscap.spec based on the Fedora spec file. We haven't add these 2 probes to the Fedora package because we don't see any benefits for the users - dpkginfo is for Debian/ubuntu and sql57 doesn't have any use case in security hardening. Do you imagine any use case?
CentOS doesn't provide the apt-devel and opendbx-devel packages. You can try to fix the broken CI it by wrapping the Requires and BuildRequires entry in the spec file by a condition, eg.
|
These dependencies enable probes which will impact the results, as far as I understand. For example, using
That's great, I just updated this PR with a commit implementing that idea. Thank you! |
The dpkg probe is being built within the Ubuntu gating job. I'd be better to actually write a probe test that would be executed there. The sql probe does not have a test and does not have any meaningful use cases (lack of auth, compatibility problems etc), it is pretty much a dead-born OVAL test. In my opinion this change would only increase CI overhead without any meaningful benefits. Unless, of course, we decide to ship Fedora package with dpkg probe enabled. |
I believe the Fedora package absolutely should be shipping with the dpkg probe enabled. Right now, if you run |
I submitted a PR against the Fedora packaging to add these dependencies: https://src.fedoraproject.org/rpms/openscap/pull-request/19 |
Okay, so, after internal meeting of Fedora packagers of
|
That sounds great! Here's a PR to the fedora packaging: https://src.fedoraproject.org/rpms/openscap/pull-request/20 And I've updated this PR accordingly. |
I'll get back to it when GH CI will recover from its coma. |
Can this PR be merged? Is there assistance I could provide to help it progress? |
The CentOS Stream 9 test is still failing. I think we should only enable it for Fedora. |
I thought I did that already, using the approach covered in #1932 (comment) However, I think that advise was slightly flawed - I think it's backwards. Instead of:
I think it should be:
I've updated this PR accordingly - how's it look now? |
Using openscap to scan a system that use apt (such as Debian or Ubuntu) returns incomplete results. This warning is logged: OVAL object 'dpkginfo_object' is not supported. The problem is that openscap is built without apt support. The fix, implemented in this commit, is to add apt as a build requirement. Only Fedora provides the apt-devel package. Therefore it is only included when building for Fedora.
The |
The problem is that openscap is built without apt support.
The fix, implemented in this commit, is to add apt as a build requirement.