Skip to content
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

clojure stuck at version 1.10.3.1040 -- can't upgrade, can't uninstall #171

Closed
nonethewizer opened this issue Mar 26, 2022 · 4 comments
Closed

Comments

@nonethewizer
Copy link

PS C:\Users\tryan> scoop status
Scoop is up to date
Update is available for:
clojure: 1.10.3.1040 -> 1.10.3.1087

PS C:\Users\tryan> scoop update clojure
clojure: 1.10.3.1040 -> 1.10.3.1087
Updating 1 outdated app:
Updating 'clojure' (1.10.3.1040 -> 1.10.3.1087) [64bit]
Downloading new version
Loading clojure-tools-1.10.3.1087.zip from cache
Checking hash of clojure-tools-1.10.3.1087.zip ... ok.
Uninstalling 'clojure' (1.10.3.1040)
WARN Shim for 'cmd-clojure' is missing. Skipping.
WARN Shim for 'cmd-clj' is missing. Skipping.
Uninstalling PowerShell module 'ClojureTools'.
Removing ~\scoop\modules\ClojureTools
ERROR Cannot bind argument to parameter 'LinkName' because it is an empty string.
ERROR This application failed to update: clojure

PS C:\Users\tryan> scoop uninstall clojure
Uninstalling 'clojure' (1.10.3.1040)
WARN Shim for 'cmd-clojure' is missing. Skipping.
WARN Shim for 'cmd-clj' is missing. Skipping.
Uninstalling PowerShell module 'ClojureTools'.
Removing ~\scoop\modules\ClojureTools
ERROR Cannot bind argument to parameter 'LinkName' because it is an empty string.

PS C:\Users\tryan> scoop checkup
No problems identified!
PS C:\Users\tryan> scoop status
Scoop is up to date
Update is available for:
clojure: 1.10.3.1040 -> 1.10.3.1087

@littleli
Copy link
Owner

Checking this. I've never seen anything like this before.

My suspicion there is some unexpected whitespace somewhere because the 'ERROR' can happen when path is not escaped and command is not parsed correctly. But which command that's open question.

@jsg24
Copy link

jsg24 commented Oct 13, 2022

I don't know exactly what's going on, but this is straight out of one of my PowerShell terminals.
image

This doesn't explain everything because I opened up a new PowerShell after this and it had reverted back to the lower version.

@littleli
Copy link
Owner

From the screenshot it seems it used the cached version. You correctly enforced update with -Sforce argument. Scoop let tools to do their work, not interfering with them if possible.

@littleli
Copy link
Owner

Closing this as there is not much I can do about this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants