What happened?
I maintain an Arch Linux package of fluux in the Arch User Repository - https://aur.archlinux.org/packages/fluux-messenger
Arch's guidelines for packaging Rust applications is to fetch dependencies with:
cargo fetch --locked --target host-tuple
This ensures crates are only pulled from the .lock file - a later build step, --frozen is passed to the Tauri build command, to ensure the lock file remains untouched, and only pre-fetched dependencies are used.
In the current release (0.15.2), the Cargo.lock file was not updated, which causes that step to fail.
The workaround is to run cargo update -w before the fetch, having this step run as part of the release process would be ideal since it ensures what's being built is exactly the same as was used while generating the release.
Steps to reproduce
cd apps/fluux/src-tauri
cargo fetch --locked --target host-tuple
Expected behavior
Cargo should fetch dependencies using the lock file
Fluux Messenger version
v0.15.2
Platform
Linux
Installation type
Other
Screenshots or logs
No response
Additional context
No response
What happened?
I maintain an Arch Linux package of fluux in the Arch User Repository - https://aur.archlinux.org/packages/fluux-messenger
Arch's guidelines for packaging Rust applications is to fetch dependencies with:
This ensures crates are only pulled from the .lock file - a later build step,
--frozenis passed to the Tauri build command, to ensure the lock file remains untouched, and only pre-fetched dependencies are used.In the current release (0.15.2), the Cargo.lock file was not updated, which causes that step to fail.
The workaround is to run
cargo update -wbefore the fetch, having this step run as part of the release process would be ideal since it ensures what's being built is exactly the same as was used while generating the release.Steps to reproduce
cd apps/fluux/src-tauri cargo fetch --locked --target host-tupleExpected behavior
Cargo should fetch dependencies using the lock file
Fluux Messenger version
v0.15.2
Platform
Linux
Installation type
Other
Screenshots or logs
No response
Additional context
No response