registry
registry copied to clipboard
Package set psc-0.15.15-20250711 (and others) broken due to deleted package
bss@monster % less packages.dhall
let upstream =
https://github.com/purescript/package-sets/releases/download/psc-0.15.15-20250711/packages.dhall
sha256:ee7af380ca58c03d51ac6bb7411ec441724c671a4fff823a2a61b1d4e345303c
in upstream
bss@monster % npx spago -q verify-set >/dev/null 2>&1; echo $?
1
bss@monster % npx spago verify-set
[... lots of output elided ...]
[info] Successfully verified "record-extra"
[info] Installing 1 dependencies.
[info] Searching for packages cache metadata..
[info] Recent packages cache metadata found, using it..
[info] Installing "record-extra-srghma"
[error]
Failed to install dependency "record-extra-srghma"
Git output:
Cloning into '.'...
fatal: could not read Username for 'https://github.com': terminal prompts disabled
Aborting installation..
[error]
Failed to install dependency "record-extra-srghma"
Git output:
Cloning into '.'...
fatal: could not read Username for 'https://github.com': terminal prompts disabled
Aborting installation..
[error]
Failed to install dependency "record-extra-srghma"
Git output:
Cloning into '.'...
fatal: could not read Username for 'https://github.com': terminal prompts disabled
Aborting installation..
[error] Installation failed
[error] Error:
[error] ExitFailure 1
Looks like this is a misleading error and the real culprit is that the package has been deleted. I am traveling but can look into it soon — in the meantime I recommend either using the non-legacy Spago if you need access to this package set or downgrading. Sorry about that!
Thanks for the quick reply. I don't need that particular set; I was just trying to update a personal project to the latest. I was able to update to 20250421, and that will be fine until we get a newer package set that does verify.