Skip to content
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

permissions: whitelist certification-sles-eal4 (bsc#1223682) #1228

Conversation

wfrisch
Copy link

@wfrisch wfrisch commented May 2, 2024

Copy link

@FilippoBonazziSUSE FilippoBonazziSUSE left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The whitelisting entry seems fine.

I am not sure where this should be submitted to, though. I guess it's fine to start with having it in Factory, but this is needed for SLE15SP6 only I imagine.

@mgerstner
Copy link
Contributor

The whitelisting entry seems fine.

I am not sure where this should be submitted to, though. I guess it's fine to start with having it in Factory, but this is needed for SLE15SP6 only I imagine.

The package seems not to exist in Factory. Therefore having it in there is unnecessary and will likely also show up as an unused whitelisting in our checker. The latter can be suppressed, but as long as no rpmlint2 based product uses this I don't thing it makes sense to place it into rpmlint2.

For SLE15-SP6 we need to whitelist this on IBS in the old rpmlint. It needs a maintenance update which will take its time.

@wfrisch
Copy link
Author

wfrisch commented May 7, 2024

The package seems not to exist in Factory. Therefore having it in there is unnecessary and will likely also show up as an unused whitelisting in our checker.
For SLE15-SP6 we need to whitelist this on IBS in the old rpmlint. It needs a maintenance update which will take its time.

@wfrisch wfrisch closed this May 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants