-
Notifications
You must be signed in to change notification settings - Fork 840
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
Stack no longer detects newest snapshot with default configuration #6516
Comments
@konn, thanks for reporting. I think Stack's default is: https://s3.amazonaws.com/haddock.stackage.org/snapshots.json and that does not seem to be up to date. Perhaps the handover of Stackage from FP Complete to the Haskell Foundation means that default needs to change. I'll make some enquiries. |
The current default was introduced in 2016: |
@chreekat, may I ask you to look at my comments above and the Reddit post. |
@chreekat gave me some input on Matrix: the default URL does need to change, and https://stackage-haddock.haskell.org/snapshots.json will likely be the most reliable one. |
@konn, this should be fixed in Stack's |
Thanks! I installed stack via ghcup as noted above and not in a hurry, so I will wait for new release. |
General summary/comments (optional)
stack new
no longer keeps track with the latest Stackage snapshots unless we specifyurls.latest-snapshot
in~/.stack/config.yaml
.Steps to reproduce
For example:
stack new --resolver nightly myproj
Expected
When run at 2024-03-11 15:35 JST, it must pick
nightly-2024-03-11
as the full snapshot name.Actual
It picks older one:
If you suspect that a Stack command misbehaved, please include the output of
that command in
--verbose
mode. If the output is larger than a page pleasepaste the output in a Gist.
On the other hand, if we add the following to
~/.stack/config.yaml
, it picks the right one:It seems that the default storage on S3 (
http://s3.amazonaws.com/haddock.stackage.org/snapshots.json
) is no longer up to date with the stackage. If this is not as intended (by Stackage maintainers), this might be a bug of Stackage, not Stack.Stack version
Method of installation
Platform
Ubuntu 20.04.6 and macOS
The text was updated successfully, but these errors were encountered: