https://bugs.documentfoundation.org/show_bug.cgi?id=164790
--- Comment #6 from CP <[email protected]> --- Thanks, everyone, for responding. Please note, however, that this isn't *only* a question of making sure that the downloadable image files are correctly named... Specifically in the case of the AppImage download, what happpens [and it was the case when I opened this ticket] is that I got a notification from my local LibreOffice client to tell me that a new version was available... I came to the LibreOffice home page, selected the AppImage download, and brought down the available file [which is not version-named]. But the "other half" of the problem here is that my LibreOffice client told me that there was a "new version" but in fact the AppImage file hadn't changed. I think that's a separate problem. Is it possible for you to ensure that ALL of the supported file formats are available at the same time? If that had been the case in this instance, I would have downloaded a non-version-numbered file, then checked it against my existing running binary [e.g. looking at the file size in bytes, and/or running a sha256sum against it. Maybe there is a second part to this ticket, which is to look at your publication process - and/or your "new version available" notification process? Maybe there is a path here were the user of an AppImage file actually doesn't get the notification *until the AppImage file version is updated*? Of course I understand that some of the above suggestions are going to require quite a lot of sophistication that needs to span your hosting and your "update checking" code in running binaries... but I think all of this should be possible. Of course, you don't need to do all of these things to solve the root problem - I think that version-naming the download images and making those versions visible at the point of download will go a long way to address my original concern. But I also think there are some really cool additional approaches you could take, if you are feeling a bit more adventurous. Thank you. -- You are receiving this mail because: You are the assignee for the bug.
