This repository has been archived by the owner on May 30, 2023. It is now read-only.
sec-policy/selinux-sssd: Downgrade to match other SELinux packages #318
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
It was my mistake during the review to allow adding a package that is much newer than the other SELinux packages we currently have. And for some reason I started getting build failures when updating packages from 2020: !!! All ebuilds that could satisfy ">=sec-policy/selinux-base-policy-2.20210908-r1" for /build/amd64-usr/ have been masked. !!! One of the following masked packages is required to complete your request: - sec-policy/selinux-base-policy-9999::coreos (masked by: missing keyword) (dependency required by "sec-policy/selinux-sssd-2.20210908-r1::portage-stable" [ebuild]) (dependency required by "sys-auth/sssd-2.3.1-r4::coreos[selinux]" [ebuild]) (dependency required by "app-admin/sudo-1.9.5_p2::coreos[sssd]" [ebuild]) (dependency required by "coreos-base/coreos-0.0.1-r302::coreos" [ebuild]) (dependency required by "coreos-base/coreos-dev-0.1.0-r81::coreos" [ebuild]) (dependency required by "coreos-devel/board-packages-0.0.1-r9::coreos" [ebuild]) (dependency required by "coreos-devel/board-packages" [argument]) It's from gentoo commit 1f7a3661f47b4da14ac3ad8c85f54f6b144104e4.
|
It is not a downgrade per-se - the same version is now built as before this change. What happened is that I synced selinux-sssd with an older version of gentoo repo, which didn't stabilize the newer versions. I don't know why I started getting those failures whereas nightlies were just fine, but still better to keep all the SELinux packages at the same version. |
jepio
approved these changes
Apr 4, 2022
JAORMX
approved these changes
Apr 4, 2022
Right, next time I'll probably do it, but I rather hope that there won't be "next time".
No worries. :) |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
It was my mistake during the review to allow adding a package that is
much newer than the other SELinux packages we currently have. And for
some reason I started getting build failures when updating packages
from 2020:
It's from gentoo commit 1f7a3661f47b4da14ac3ad8c85f54f6b144104e4.
CC: @JAORMX
CI: It is a part of package updates, 2020 edition - http://localhost:9091/job/os/job/manifest/5298/cldsv/