SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** nostromo reported on #krita (13 October 2022) 16:50:14 <nostromo426> ehlo. i use appImage to run krita, and to keep the images up to date, i use an appimage called "appimageupdatetool", which reads information from the appimage to be updated, and extracts a zsync-url. for krita this fails, because the extracted zsync-url is pointing to "https://download.kde.org/stable/krita/updates/Krita-Stable-x86_64.appimage.zsync", which on the webserver 16:50:19 "https://download.kde.org/stable/krita/updates/Krita-stable-x86_64.appimage.zsync" (notice the lower-case "s" in "stable") is available. since i do not know where to report this, i thought i place it here. 16:50:48 s/which on/while on/ STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION
I just changed this on the server...
The problem is simply that the zsync files aren't generated with the string "Stable" but "CHANGEME", and I often forget to rename that to Stable instead of stable on the download site when doing a release. I have a thorough distaste for the CaMeLcApS appimage likes... Maybe we can fix the scripts that create the artfacts, or postpone that to until after the move to invent.
The zsync files are now correctly generated.