Skip to content

Package set psc-0.15.15-20250711 (and others) broken due to deleted package #523

Closed

Description

@stephen-smith
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

Activity

  1. changed the title [-]Package set asc-0.15.15-20250711 (and others) is broken without GitHub authentication[/-] [+]Package set psc-0.15.15-20250711 (and others) is broken without GitHub authentication[/+] on Jul 27, 2025
  2. thomashoneyman commented on Jul 27, 2025

    @thomashoneyman
    Member

    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!

  3. stephen-smith commented on Jul 27, 2025

    @stephen-smith
    Author

    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.

  4. changed the title [-]Package set psc-0.15.15-20250711 (and others) is broken without GitHub authentication[/-] [+]Package set psc-0.15.15-20250711 (and others) broken due to deleted package[/+] on Jul 28, 2025
  5. thomashoneyman commented on Feb 1, 2026

    @thomashoneyman
    Member

    Closing this issue as package sets are treated as immutable. We can't do anything about deleted packages in legacy package sets, but if you switch to spago@1.x.x then it uses registry package sets backed by registry storage, from which packages cannot be deleted except due to security issues.

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions