AppImageUpdate
AppImageUpdate copied to clipboard
AppImageCommunity
AppImageUpdate lets you update AppImages in a decentral way using information embedded in the AppImage itself.
So, I discovered this issue when I was trying to install the Pling Store from https://www.opendesktop.org/p/1175480/ (i have OCS-URL installed via my package manager as a pre-requisite) but... it also...
 When updating an unsigned AppImage the loading bar turns yellow and there is a message about a "problem". At least to me this makes it seem like it failed...
**AppImageUpdate-x86_64.AppImage**  Details: ``` Fetching release information for tag "continuous" from GitHub API. Updating from GitHub Releases via ZSync zsync2: /home/user/.local/bin/AppImageUpdate-x86_64.AppImage found, using as seed file zsync2: Target file: /home/user/.local/bin/AppImageUpdate-x86_64.AppImage...
Basically I got this error message every time I try to update some AppImage using AppImageUpdate or appimageupdatetool from this repo. For simplicity I run appimageupdatetool with self update flag....
On fedora the crt file is present as ca-bundle.crt and not as ca-certificates.crt, so zsync2 error is shown as ``` Checking for updates... zsync2: error setting certificate verify locations: CAfile:...
Log: Fetching latest release information from GitHub API Fetching latest release information from GitHub API Fetching latest release information from GitHub API Updating from GitHub Releases via ZSync zsync2: /applications/VSCodium-1.60.0-1630974030.glibc2.17-x86_64.AppImage.part...
zsync2: Downloading from https://github-releases.githubusercontent.com/144590939/293ea170-346b-48a6-8df0-d213e9e76b2c?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAIWNJYAX4CSVEH53A%2F20210810%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20210810T130921Z&X-Amz-Expires=300&X-Amz-Signature=d5d54e732c72970fac41ceb266439fc51b65505af4291e4c1a60bba1df822b63&X-Amz-SignedHeaders=host&actor_id=0&key_id=0&repo_id=144590939&response-content-disposition=attachment%3B%20filename%3DVSCodium-1.59.0-1628208101.glibc2.17-x86_64.AppImage&response-content-type=application%2Foctet-stream zsync2: optimized ranges, old requests count 78, new requests count 10 zsync2: failed to retrieve from VSCodium-1.59.0-1628208101.glibc2.17-x86_64.AppImage, status -1
if `appimageupdatetool` is given a relative path to the AppImage, `-r` removes the freshly updated `.AppImage` (and keeps `.AppImage.zs-old`): ``` $ appimageupdatetool -r XXXXXXXXXX-latest-x86_64.AppImage Checking for updates... ... done! Starting...
**Background:** When I use an appimage, I usually keep a `.home` and `.config` directory beside it so that files created by that appimage doesn't get into my user home directory...
When running appimageupdatetool on an AppImage I just created, I get: ``` motofckr9k@motofckr9k-mint-desktop:~/Vircadia$ ./appimageupdatetool-x86_64.AppImage -j Vircadia-x86_64-release-latest.AppImage qt5ct: using qt5ct plugin zsync2: zsync2: Reading and/or parsing .zsync file failed! Error checking...
Metadata
Owner
Metadata
AppImageUpdate lets you update AppImages in a decentral way using information embedded in the AppImage itself.