You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are lots of packages that are only available in c8s and c9s buildroot but not in the compose. This affects packages like SSSD, we have to add buildroot repository manually as a workaround. I think it would be good to automatically fallback to the repository if some dependencies are not satisfied.
Copr just uses mock-core-configs, so this should be ideally filled against
the mock project.
I don't really like the "fallback" idea. Builds should be reproducible, so
it means a fixed set of repositories (buildroot contains a different set of
packages, potentially competing with the released variants). Adding a Koji
buildroot repo unconditionally isn't something we'd like to do.
Long-term, we should report all those missing parts to Red Hat, that those
packages are actually needed - and should be added to composes.
FTR, we don't have an RFE for this, but I was thinking about making available the
"local" mock-core-configs as opt-in. The configs have the buildroot repository,
but are disabled. https://pagure.io/fedora-infrastructure/issue/9480
The text was updated successfully, but these errors were encountered:
Original issue: https://pagure.io/copr/copr/issue/2067
Opened: 2022-02-02 11:25:46
Opened by: pbrezina
There are lots of packages that are only available in c8s and c9s buildroot but not in the compose. This affects packages like SSSD, we have to add buildroot repository manually as a workaround. I think it would be good to automatically fallback to the repository if some dependencies are not satisfied.
https://kojihub.stream.centos.org/kojifiles/repos/c9s-build/latest/$basearch/
https://koji.mbox.centos.org/kojifiles/repos/dist-c8-stream-build/latest/$basearch/
praiskup commented at 2022-02-02 12:34:40:
Copr just uses
mock-core-configs
, so this should be ideally filled againstthe mock project.
I don't really like the "fallback" idea. Builds should be reproducible, so
it means a fixed set of repositories (buildroot contains a different set of
packages, potentially competing with the released variants). Adding a Koji
buildroot repo unconditionally isn't something we'd like to do.
Long-term, we should report all those missing parts to Red Hat, that those
packages are actually needed - and should be added to composes.
@jwboyer ideas on this?
praiskup commented at 2022-02-02 13:52:48:
FTR, we don't have an RFE for this, but I was thinking about making available the
"local" mock-core-configs as opt-in. The configs have the buildroot repository,
but are disabled. https://pagure.io/fedora-infrastructure/issue/9480
The text was updated successfully, but these errors were encountered: