-
Notifications
You must be signed in to change notification settings - Fork 1.5k
[Bug]: autohotkey appears to be installing an old version #15337
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
@HUMORCE Thank you for checking on this. The results I experience are different. I uninstalled and reinstalled AHK (via Scoop) multiple times, just to be sure, and the result was the same each time. I also verified the |
Try execute them and leave the outputs. |
scoop cat "$(scoop prefix autohotkey)\manifest.json" |
scoop cat "$(scoop prefix autohotkey)\install.json" |
Here is the list of files the ..\scoop\apps\autohotkey\2.0.19 |
Looks like something went wrong with the install script? Try a fresh install, ! this will remove persisted data of autohotkey:
|
@HUMORCE wrote:
That fixed it. Thank you! Now let's take a quick moment to look to see if there is anything to improve:
|
I can confirm that it could work well at latest in Jun, 2024. Persistence is primarily keeping installed versions(see notes of the manifest) Even now, as I install/update between multiple versions, I can't reproduce the problem you report.
It created while updating/uninstalling: Lines 54 to 57 in 3ecdbe8
|
@HUMORCE wrote:
Hmmm... I'll keep an eye on it as future versions of autohotkey are released. Thank you for checking and performing that testing.
|
https://github.com/ScoopInstaller/Scoop/wiki/Pre-Post-(un)install-scripts
|
Prerequisites
Package Name
autohotkey
Expected/Current Behaviour
When installing autohotkey, v2.0.19 is currently supposed to be installed. However, according to the date of the executable, the executable's meta data, and the autohotkey help file, v2.0.18 is actually being installed.
Furthermore, the file structure Scoop is creating is quite odd. It creates a folder named v2.0.18 within the a folder named v2.0.19.
I tried uninstalling and reinstalling autohotkey multiple times (via Scoop), and the result was always the same.
Steps to Reproduce
scoop install autohotkey
Possible Solution
I haven't had time to look into a fix. Either upstream didn't update their file timestamps and metadata, or something Scoop is doing for autohotkey is borked. I'm guessing it's the latter because all the info matches what one would expect for v2.0.18 instead of v2.0.19.
Sorry, I haven't had time to look into things further.
Scoop and Buckets Version
Scoop Config
PowerShell Version
Additional Softwares
No response
The text was updated successfully, but these errors were encountered: