-
Notifications
You must be signed in to change notification settings - Fork 32
Description
I made this test repo so you can see the issue better: https://github.com/Samueru-sama/SpeedCrunch-AppImage-test/tree/main
The repo makes 2 appimages here:
-
One AppImage is made using the distros zsync make. No problems here.
-
The other gets made by downloading the zsyncmake2 appimage and adding it to PATH. This is how it is meant to be used right?
-
appimageupdatetool version 1-alpha (commit 98633fe), build 234 built on 2025-02-15 13:07:16 UTC
-
SpeedCrunch-0.12-distrozsync-x86_64.AppImage sha256: 9a01c36bfb7dfe799448f8394c514b33bfe210cb3f168e937ed6349638d59d05
-
SpeedCrunch-0.12-zsync2-x86_64.AppImage sha256: 16c3c56f37fe7ee9f2b5a4b218abece6c7dc11351f8fa3a4e0fe48464794f0c8
Issue
After downloading the two AppImages, this is what happens when I use appimageupdatetool on them, nothing should happen since they are the latest version:
-
appimageupdatetool correctly says
Update not required, exiting.
for the appimage made with my distro's zsyncmake. -
However when tried on the zsync2 AppImage, it gets updated somehow, and the sha256 changes to a new one: e7d1633bbb75f07c7876709328dbb25ea16da73de566d477c3bba2687e5bbba0