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

dockerfile: packaging: Fix build check for centos-7 and failures of package creations #9043

Merged
merged 4 commits into from
Jul 5, 2024

Conversation

cosmo0920
Copy link
Contributor

Due to EOL of CentOS7 in the end of last month, we need to use vault repo to obtain CentOS 7 packages.


Enter [N/A] in the box, if an item is not applicable to your change.

Testing
Before we can approve your change; please submit the following in a comment:

  • Example configuration file for the change
  • Debug log output from testing the change
  • Attached Valgrind output that shows no leaks or memory corruption was found

If this is a change to packaging of containers or native binaries then please confirm it works for all targets.

  • Run local packaging test showing all targets (including any new ones) build.
  • Set ok-package-test label to test for all targets (requires maintainer to do).

Documentation

  • Documentation required for this feature

Backporting

  • Backport to latest stable release.

Fluent Bit is licensed under Apache 2.0, by submitting this pull request I understand that this code will be released under the terms of that license.

@cosmo0920 cosmo0920 marked this pull request as ready for review July 4, 2024 04:46
@cosmo0920
Copy link
Contributor Author

cosmo0920 commented Jul 4, 2024

In addition, EPEL repo is not moved to use vault. So, we needn't touch it.

@patrick-stephens
Copy link
Contributor

You don't typically need yum update as it is implicitly done, unlike apt, but it won't hurt.

@patrick-stephens patrick-stephens added ok-package-test Run PR packaging tests and removed docs-required labels Jul 4, 2024
@patrick-stephens
Copy link
Contributor

@cosmo0920 it looks like we have some failures: https://github.com/fluent/fluent-bit/actions/runs/9791908413/job/27037013628?pr=9043

@edsiper
Copy link
Member

edsiper commented Jul 4, 2024

@cosmo0920
Copy link
Contributor Author

Oh, we have to handle packaging side of Dockerfile.

@cosmo0920 cosmo0920 changed the title dockerfile: centos7: Follow repository URL change due to CentOS7 EOL dockerfile: packaging: Fix build check for centos-7 and failures of package creations Jul 5, 2024
Signed-off-by: Hiroshi Hatake <hiroshi@chronosphere.io>
Signed-off-by: Hiroshi Hatake <hiroshi@chronosphere.io>
Signed-off-by: Hiroshi Hatake <hiroshi@chronosphere.io>
@cosmo0920 cosmo0920 force-pushed the cosmo0920-fix-centos-7-dockefile branch 3 times, most recently from ed7295b to 1ba0b87 Compare July 5, 2024 05:59
@cosmo0920
Copy link
Contributor Author

I sent patches luajit-cmake which are modified in this PR on zhaozg/luajit-cmake#9.

Signed-off-by: Hiroshi Hatake <hiroshi@chronosphere.io>
@cosmo0920 cosmo0920 force-pushed the cosmo0920-fix-centos-7-dockefile branch from 1ba0b87 to dcb38b4 Compare July 5, 2024 06:55
@patrick-stephens
Copy link
Contributor

@edsiper shall we disable CentOS 7 ARM builds until the PR is merged upstream?

@edsiper
Copy link
Member

edsiper commented Jul 5, 2024

@cosmo0920 there are some luajit stuff in the commits

@edsiper
Copy link
Member

edsiper commented Jul 5, 2024

well, its ok to rebase...

@edsiper edsiper merged commit 7ee1b35 into master Jul 5, 2024
69 of 70 checks passed
@edsiper edsiper deleted the cosmo0920-fix-centos-7-dockefile branch July 5, 2024 18:30
@edsiper
Copy link
Member

edsiper commented Jul 5, 2024

thank you!

@cosmo0920 cosmo0920 restored the cosmo0920-fix-centos-7-dockefile branch July 11, 2024 07:51
@cosmo0920 cosmo0920 deleted the cosmo0920-fix-centos-7-dockefile branch July 11, 2024 07:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ok-package-test Run PR packaging tests
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants