Fix Bootloader installation #2032
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
svartkanin
changed the title
Closed
|
Great catch! |
Torxed
approved these changes
Sep 13, 2023
This was referenced Sep 18, 2023
|
I believe this fix is important enough to get a new Arch ISO release with it. |
|
This and a few other fixes are critical enough for a new release yes. But hopefully by the weekend the new release drops! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This fixes:
When installing the bootloader, the respective device was searched by the boot partition path. However, the search was only conducted on the in-memory device cache which is not updated after any partitioning and will therefore not contain the newly created partitions.
We'll have therefore have to retrieve the parent partition path from a new lsblk call.