You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Package set psc-0.15.15-20250711 (and others) broken due to deleted package #523
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
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.
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
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.
Activity
[-]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[/+]thomashoneyman commentedon Jul 27, 2025
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!
stephen-smith commentedon Jul 27, 2025
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.
[-]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[/+]thomashoneyman commentedon Feb 1, 2026
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.xthen it uses registry package sets backed by registry storage, from which packages cannot be deleted except due to security issues.