Use official AppImage extraction instead of unappimage#111
Open
Pragadesh-45 wants to merge 1 commit into
Open
Conversation
|
🚧 Test build enqueued. |
|
🚧 Started test build. |
|
✅ Test build succeeded. To test this build, install it from the testing repository: Built for x86_64 architecture. |
|
🚧 Test build enqueued. |
|
🚧 Started test build. |
|
🚧 Test build enqueued. |
|
❌ Test build was cancelled. Help
|
|
🚧 Started test build. |
|
✅ Test build succeeded. To test this build, install it from the testing repository: Built for x86_64 architecture. |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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 PR replaces the use of
unappimagewith the AppImage’s built-in extraction mechanism:The AppImage runtime provides its own extraction method (
--appimage-extract) which more accurately reproduces the original filesystem layout compared to third-party tools likeunappimage.While
unappimageworks in most cases, it can introduce subtle differences during SquashFS extraction (e.g. padding or alignment changes). These differences don’t affect normal execution of Bruno, but they can cause inconsistencies when inspecting files at the byte level (for example, when validating.asarintegrity or offsets).