Closed pbb72 closed 9 months ago
This feature is not guaranteed to be 100% available
A known and documented issue.
A known and documented issue.
That is an extremely minimalist reply to close a bug report with. Known?? By whom? Definitely not by me. Documented?? Where? I didn't come across any.
If this is indicated anywhere, then surely this bug is still valid in pointing out the documentation is lacking in findability.
I tagged the issue as wating feedback over 2 weeks, you stayed silent until I close it.
https://github.com/ScoopInstaller/Scoop/issues/3045 https://github.com/ScoopInstaller/Scoop/issues/3894
If this case, you can just skip hash check by command options.
You were waiting for feedback from me? Feedback on what, there was no question asked.
Also, you should be aware that GitHub does not send out notifications about added labels. So, the only notification I got was you saying This feature is not guaranteed to be 100% available.
and two weeks later A known and documented issue.
If you think I'm being rude about this, I am sorry. I am just waiting for how you're going to respond to my first reply.
You can skip the hash check for scoop install
or scoop download
and subscribe related issues in Core repo(see pre-reply).
No problem, you were not rude but just quicker to process this problem than I am. I know I am not the most tactful either. No harm meant. Thanks for the links to other issues for installing old versions, I now understand it's not a clear-cut as I thought it was. I will try skipping the hash-check next time!
Prerequisites
Package Name
vscode
Expected/Current Behaviour
scoop install vscode@1.70.2
should install v.1.70.2Instead, of gives an hash check failed error.
Steps to Reproduce
Possible Solution
It seems to me that the hash is always checked against the newest version, which of course fails for older versions.
Scoop and Buckets Version
Scoop Config
PowerShell Version
Additional Softwares
No response