Skip to content

Unable to install cabal-install-3.8.0.20220526 on Windows #8210

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

Closed
cydparser opened this issue Jun 11, 2022 · 16 comments
Closed

Unable to install cabal-install-3.8.0.20220526 on Windows #8210

cydparser opened this issue Jun 11, 2022 · 16 comments

Comments

@cydparser
Copy link
Collaborator

cydparser commented Jun 11, 2022

Describe the bug

ghcup fails to install the prerelease version of cabal-install. The error indicates that a file named cabal.exe was not found. The zip file contains a file named cabal (without an extension).

To Reproduce

ghcup config add-release-channel https://raw.githubusercontent.com/haskell/ghcup-metadata/master/ghcup-prereleases-0.0.7.yaml
ghcup install cabal 3.8.0.20220526 

Resulted in:

Error: (Unable to copy a file. Reason was: C:\Users\cyd\AppData\Local\Temp\ghcup-c840ea7fe45060fc\cabal.exe: copyFile:atomicCopyFileContents:withReplacementFile:copyFileToHandle:openBinaryFile: does not exist (No such file or directory),
 The version 3.8.0.20220526 of the tool cabal is not installed.)

System information

  • Windows 11
  • GHCup v0.1.17.8-p1
@ulysses4ever
Copy link
Collaborator

This an unfortunate but known oversight, see #8191. Should be fixed in the future (pre)releases. I'm not sure though why this pre-release hasn't been fixed.

@Mikolaj
Copy link
Member

Mikolaj commented Jun 13, 2022

This an unfortunate but known oversight, see #8191. Should be fixed in the future (pre)releases.

Correct.

I'm not sure though why this pre-release hasn't been fixed.

I'm guessing, we didn't want to break the checksums? Not sure.

@Mikolaj
Copy link
Member

Mikolaj commented Jun 13, 2022

@hasufell: is there a non-dirty way of working around that problem in ghcup (by the user or by us)?

@hasufell
Copy link
Member

@hasufell: is there a non-dirty way of working around that problem in ghcup (by the user or by us)?

We you fix the bindist manually and upload it as -p1 as a new tarball.

@Mikolaj
Copy link
Member

Mikolaj commented Jun 13, 2022

I do that (with a new signed file containing the new single checksum?) and what happens next? How does that help?

@hasufell
Copy link
Member

I do that (with a new signed file containing the new single checksum?) and what happens next? How does that help?

You upload it?

@Mikolaj
Copy link
Member

Mikolaj commented Jun 13, 2022

OK, I fix, name with suffix -p1, checksum, sign, upload to the same directory as the previous 3.8.0.20220526 archives. Correct? Then what? I'd like to understand, so that I don't make wrong assumptions and silly mistakes.

@hasufell
Copy link
Member

OK, I fix, name with suffix -p1, checksum, sign, upload to the same directory as the previous 3.8.0.20220526 archives. Correct? Then what? I'd like to understand, so that I don't make wrong assumptions and silly mistakes.

Then you wait for me to get sober and update ghcup metadata.

@Mikolaj
Copy link
Member

Mikolaj commented Jun 13, 2022

OK, I fix, name with suffix -p1, checksum, sign, upload to the same directory as the previous 3.8.0.20220526 archives. Correct? Then what? I'd like to understand, so that I don't make wrong assumptions and silly mistakes.

Done. (CDN may take some hours.)

Then you wait for me to get sober and update ghcup metadata.

How do we catch that short window of opportunity?

@Mikolaj
Copy link
Member

Mikolaj commented Jun 15, 2022

@hasufell: respectful ping?

@hasufell
Copy link
Member

Ping me tomorrow again 🍻

@Mikolaj
Copy link
Member

Mikolaj commented Jun 17, 2022

Good times! :D

hasufell added a commit to haskell/ghcup-metadata that referenced this issue Jun 17, 2022
@hasufell
Copy link
Member

Done: haskell/ghcup-metadata@437a84e

@Mikolaj
Copy link
Member

Mikolaj commented Jun 17, 2022

Julian, thank you so much. @cydparser. please let us know if this works for you.

@cydparser
Copy link
Collaborator Author

It works, thanks!

@Mikolaj
Copy link
Member

Mikolaj commented Jun 20, 2022

Success! Thank you all.

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

No branches or pull requests

4 participants