https://bugs.winehq.org/show_bug.cgi?id=50083 Anastasius Focht <focht(a)gmx.net> changed: What |Removed |Added ---------------------------------------------------------------------------- URL| |https://web.archive.org/202 | |10124131534/https://github. | |com/ASCOMInitiative/ASCOMPl | |atform/releases/download/v6 | |.5SP1Release/ASCOMPlatform6 | |5SP1.exe Ever confirmed|0 |1 CC| |focht(a)gmx.net Status|UNCONFIRMED |NEW Keywords| |download, Installer Component|-unknown |advapi32 --- Comment #3 from Anastasius Focht <focht(a)gmx.net> --- Hello folks, confirming on behalf of OP. There is a patch posted to wine-devel, mentioning "ASCOM Platform installer": https://www.winehq.org/pipermail/wine-devel/2021-January/179654.html It doesn't reference this bug id explicitly though. --- Generate notes on creating backups/snapshots since you posted download links to github in your comment #0 ... When creating a ticket I recommend that you immediately create a snapshot of the artifact using Internet Archive (archive.org). https://addons.mozilla.org/en-US/firefox/addon/wayback-machine_new/ Github is not a "safe backup" when comes to binary release assets. Various Github projects purge their assets after new releases - even if they are hosted on AWS CDN. This makes it hard to retest / reproduce bugs any time. Example of ASCOM Platform 6.5 release from your comment #0: https://github.com/ASCOMInitiative/ASCOMPlatform/releases/tag/v6.5Release https://github.com/ASCOMInitiative/ASCOMPlatform/releases/download/v6.5Relea... = broken download link Binary release assets are gone, source code tarball is still there in project assets. Latest release ASCOM Platform 6.5 - Service Pack 1: https://github.com/ASCOMInitiative/ASCOMPlatform/releases/tag/v6.5SP1Release Binary release assets are hosted on AWS CDN, source code tarballs in project assets. https://github.com/ASCOMInitiative/ASCOMPlatform/releases/download/v6.5SP1Re... (valid as of today, 20210124) --- There is the possibility to archive things using Github mechanics but that's on the project owner/developer responsibility. Never rely on that - even if archived assets exist in the project - they can be still purged as well. I've created a snapshot via Internet Archive here: https://web.archive.org/20210124131534/https://github.com/ASCOMInitiative/AS... Note, when you encounter AWS or similar CDN's that encode a lot of parameters in the final URL, there is a trick to construct a "sane" URL after the snapshot has been created: https://web.archive.org/<datetimestamp>/<original-url> Replace '<datetimestamp>' from the snapshot date. When visiting the link for download you will briefly see: --- snip --- Loading... https://github.com/ASCOMInitiative/ASCOMPlatform/releases/download/v6.5SP1Re... | 13:14:35 January 24, 2021 Got an HTTP 302 response at crawl time Redirecting to... https://github-production-release-asset-2e65be.s3.amazonaws.com/131588847/60... --- snip --- It will still resolve to the original artifact. Above information is generic and probably belongs to a Wiki but well ;-) $ sha1sum ASCOMPlatform65SP1.exe 7b0d5f8f8cdda70c9fc3da93283451f34ec3b94d ASCOMPlatform65SP1.exe $ du -sh ASCOMPlatform65SP1.exe 59M ASCOMPlatform65SP1.exe $ wine --version wine-6.0 Regards -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.