Skip to content

fix: resolve #365 — AppImage build fails - #727

Open
chinhkrb113 wants to merge 2 commits into
jpochyla:mainfrom
chinhkrb113:improve/quality/update-or-replace-appimage-ingredients-c
Open

fix: resolve #365 — AppImage build fails#727
chinhkrb113 wants to merge 2 commits into
jpochyla:mainfrom
chinhkrb113:improve/quality/update-or-replace-appimage-ingredients-c

Conversation

@chinhkrb113

Copy link
Copy Markdown

Summary

The pkg2appimage-ingredients.yml file defines how the AppImage is assembled. If the project switches from pkg2appimage to linuxdeploy, this file may no longer be needed. If keeping pkg2appimage, the ingredients file may need updates to reference correct package sources or binary paths

Fixes #365

Changes

  • .pkg/APPIMAGE/pkg2appimage-ingredients.yml

Why

.pkg/APPIMAGE/pkg2appimage-ingredients.yml: The pkg2appimage-ingredients.yml file defines how the AppImage is assembled. If the project switches from pkg2appimage to linuxdeploy, this file may no longer be needed. If keeping pkg2appimage, the ingredients file may need updates to reference correct package sources or binary paths.

Fixes jpochyla#365

Signed-off-by: ChinhLee <76194645+chinhkrb113@users.noreply.github.com>
@jacksongoode

Copy link
Copy Markdown
Collaborator

@chinhkrb113 Were you able to build and run the AppImage that resulted from this run?

@jacksongoode jacksongoode left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks good but let's confirm this indeed builds & runs?

@chinhkrb113

Copy link
Copy Markdown
Author

@jacksongoode I pushed an update that restores the AppImage workflow and adds a smoke test for the generated AppImage.

The changes now:

  • re-enable the AppImage job
  • download the amd64 Debian artifact correctly
  • select the x86_64 pkg2appimage binary explicitly
  • fix the AppImage recipe metadata and paths
  • launch the generated AppImage under xvfb as a CI smoke test

I also verified the local checks: cargo test --workspace --locked, cargo clippy --workspace --locked -- -D warnings, YAML parsing, and packaging checks all pass.

@chinhkrb113
chinhkrb113 requested a review from jacksongoode July 6, 2026 11:29
@jacksongoode

Copy link
Copy Markdown
Collaborator

Do we need this "Smoke Test AppImage" I think cleaning up this PR so its exclusively only the minimal changes necessary to get the build working would be nice.

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.

AppImage build fails

2 participants