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

bootloader: Don't abort patching if grub.cfg is empty #220

Merged
merged 1 commit into from Nov 25, 2019

Conversation

olysonek
Copy link
Contributor

Previously, if the grub.cfg patching code ran into a grub.cfg file that was empty, all subsequent grub.cfg files would get skipped and would not be patched. This behaviour doesn't make much sense to me. We should skip empty grub.cfg files and patch all the non-empty ones.

Resolves: rhbz#1622646

Previously, if the grub.cfg patching code ran into a grub.cfg file
that was empty, all subsequent grub.cfg files would get skipped and
would not be patched. This behaviour doesn't make much sense to me. We
should skip empty grub.cfg files and patch all the non-empty ones.

Resolves: rhbz#1622646
@packit-as-a-service
Copy link

Congratulations! The build has finished successfully. 🍾

You can install the built RPMs by following these steps:

  • sudo yum install -y dnf-plugins-core on RHEL 8
  • sudo dnf install -y dnf-plugins-core on Fedora
  • dnf copr enable packit/redhat-performance-tuned-220
  • And now you can install the packages.

Please note that the RPMs should be used only in a testing environment.

@yarda
Copy link
Contributor

yarda commented Nov 25, 2019

OK, thanks, merged.

@yarda yarda merged commit 6813222 into redhat-performance:master Nov 25, 2019
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.

None yet

2 participants