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.

Sign up for GitHub

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

Jump to bottom

Switch workers to Fedora to support newer macros #613

Open
lachmanfrantisek opened this issue Nov 21, 2024 · 2 comments
Open

Switch workers to Fedora to support newer macros #613

lachmanfrantisek opened this issue Nov 21, 2024 · 2 comments
Labels
area/fedora Related to Fedora ecosystem complexity/single-task Regular task, should be done within days. gain/high This brings a lot of value to (not strictly a lot of) users. high-prio High priority. kind/internal Doesn't affect users directly, may be e.g. infrastructure, DB related.

Comments

@lachmanfrantisek
Copy link
Member

lachmanfrantisek commented Nov 21, 2024 •
edited
Loading

Since people started using new macros RPM functionalities that are not available (and probably won't be) on CentOS Stream 9, let's switch our workers to Fedora to help in this situation.

Long-term, we need to research how to provide matching environment: packit/research#219
@lachmanfrantisek lachmanfrantisek mentioned this issue Nov 21, 2024
Open
@nforro
Copy link
Member

nforro commented Nov 21, 2024

Since people started using new macros that are not available (and probably won't be) on CentOS Stream 9, let's switch our workers to Fedora to help in this situation.

It's not about macros (that can be handled e.g. with mock or just by preparing a suitable environment for rpm), it's about new rpm features that won't be available in older/more stable distributions.

When we switch to rpm 4.20, spec files using %patchN syntax will become unparseable, however that shouldn't be a problem on Fedora where all packages have been mass-converted, though it could be an issue on CentOS Stream.

@lachmanfrantisek lachmanfrantisek added high-prio High priority. area/fedora Related to Fedora ecosystem complexity/single-task Regular task, should be done within days. gain/high This brings a lot of value to (not strictly a lot of) users. kind/internal Doesn't affect users directly, may be e.g. infrastructure, DB related. labels Nov 25, 2024
@lachmanfrantisek lachmanfrantisek moved this from new to priority-backlog in Packit Kanban Board Nov 25, 2024
@nforro nforro mentioned this issue Nov 25, 2024
Closed
@lachmanfrantisek
Copy link
Member Author

Please, try running tests before deployment.

@lachmanfrantisek lachmanfrantisek moved this from priority-backlog to refined in Packit Kanban Board Nov 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/fedora Related to Fedora ecosystem complexity/single-task Regular task, should be done within days. gain/high This brings a lot of value to (not strictly a lot of) users. high-prio High priority. kind/internal Doesn't affect users directly, may be e.g. infrastructure, DB related.
Projects
Packit Kanban Board
Status: refined
Milestone
No milestone
Development

No branches or pull requests
2 participants
@nforro @lachmanfrantisek