Skip to content

Conversation

@ppisar
Copy link
Contributor

@ppisar ppisar commented Oct 6, 2025

It requires yaml-cpp ≥ 0.7.0 and swig ≥ 4.2.0 which do not exist in RHEL 9. The team decided on 2025-10-06 meeting that libpkgmanifs won't be supported there.

It requires yaml-cpp ≥ 0.7.0 and swig ≥ 4.2.0 which do not exist in
RHEL 9. The team decided on 2025-10-06 meeting that libpkgmanifs won't
be supported there.
@ppisar ppisar requested a review from kontura October 6, 2025 14:09
@kontura
Copy link
Contributor

kontura commented Oct 8, 2025

I believe this will not work.
The distgit-overrides are used to override distgit config for a particular chroot it doesn't disable the rest (it also requires more mandatory settings).

Looking into rpm-gitoverlay I don't think there is a way to disable particular chroot(s) only for some component(s).
Hopefully we will get more flexibility after switching to packit: #1751.

I did look into the nightly builds and it seems maybe half? of the components are also failing on centos-stream+epel-next-9-x86_64 and epel-9-x86_64 . Perhaps we could disable those chroots for the whole COPR project?

@ppisar
Copy link
Contributor Author

ppisar commented Oct 10, 2025

I believe this will not work. The distgit-overrides are used to override distgit config for a particular chroot it doesn't disable the rest (it also requires more mandatory settings).

Looking into rpm-gitoverlay I don't think there is a way to disable particular chroot(s) only for some component(s).

Ok.

Hopefully we will get more flexibility after switching to packit: #1751.

I did look into the nightly builds and it seems maybe half? of the components are also failing on centos-stream+epel-next-9-x86_64 and epel-9-x86_64 . Perhaps we could disable those chroots for the whole COPR project?

I'd like to keep building for RHEL 9 as much as component as possible to be sure we do not break building there. To ease backporting to rhel branches. To test and discover problems early as possible.

@ppisar ppisar closed this Oct 10, 2025
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.

2 participants