Skip to content

Fix deb/rpm bundling: desktop file path must be relative to tauri.conf.json - #44

Merged
setzor merged 1 commit into
mainfrom
vibe/deb-desktop-file-path-0af59b
Oct 23, 2026
Merged

setzor merged 1 commit into
mainfrom
vibe/deb-desktop-file-path-0af59b

Conversation

@setzor

@setzor setzor commented Oct 23, 2026

Copy link
Copy Markdown
Owner

Summary

  • The v0.1.2 Linux release run got further this time: dependencies installed, Rust compiled, and the AppImage bundled successfully — then the deb step failed with Failed to copy custom files: "src-tauri/desktop/com.veldnotes.app.desktop" does not exist
  • Root cause: the bundler resolves bundle > deb/rpm > files source paths relative to the tauri.conf.json location (per the Tauri docs), so the leading src-tauri/ doubled the path
  • Fix: change both mappings (deb + rpm) from src-tauri/desktop/com.veldnotes.app.desktop to desktop/com.veldnotes.app.desktop

Verification

  • Config-only change, confirmed against the Tauri v2 Debian docs ("the path to the file on your filesystem, relative to the tauri.conf.json file")
  • After merging, re-pushing the v0.1.2 tag should complete all three Linux bundles (AppImage, DEB, RPM) plus the MSI, all attached to the draft release

The Linux release build compiled and even bundled the AppImage, but
the deb step failed with 'Failed to copy custom files: src-tauri/
desktop/com.veldnotes.app.desktop does not exist'. The bundler
resolves bundle file mappings relative to the tauri.conf.json
location, so the leading src-tauri/ doubled the path. Per the Tauri
docs (bundle > deb > files), source paths must be relative to the
config file - use desktop/com.veldnotes.app.desktop.

Co-authored-by: setzor <setzor@users.noreply.github.com>
@setzor
setzor marked this pull request as ready for review October 23, 2026 19:04
@setzor
setzor merged commit ac673ee into main Oct 23, 2026
2 checks passed
@setzor
setzor deleted the vibe/deb-desktop-file-path-0af59b branch October 23, 2026 19:04
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.

2 participants