Visitar URL original
Snapshot index tarball no longer generated · Issue #330 · commercialhaskell/stackage-server · GitHub
Skip to content

Snapshot index tarball no longer generated #330

Open

Description

@chreekat

A random index tarball from olden times: https://www.stackage.org/lts-13.11/00-index.tar.gz

(Downloads fine)

The same route for a newer LTS: https://www.stackage.org/lts-22.6/00-index.tar.gz

(Redirects to https://stackage-haddock.haskell.org/package-index/lts-22.6.tar.gz, which returns a 404)


I'm not sure whether this is a "bug". I'm okay with this endpoint being deprecated. A nicer error might be nice, though. And a newer way to integrate cabal-install with snapshots-as-repositories would also be good.

Activity

  1. added
    incidentPublic tracking of Stackage incidents and outages.
    on Jul 9, 2025
  2. shlevy commented on Jan 19, 2026

    @shlevy

    Was hoping to use the snapshot "package-repo" as a way to integrate with cabal.project, would be nice to bring this back/modernize it.

  3. chreekat commented on Jan 19, 2026

    @chreekat
    MemberAuthor

    @commercialhaskell/stackage-curators do you know if this tarball is simply not generated at all, or if the new infrastructure just doesn't make it easily accessible? I vaguely recall creating this ticket, but I don't remember the context.

  4. shlevy commented on Jan 19, 2026

    @shlevy

    Perhaps the overhead is too high, but ideally we’d create a new-style hackage repo (01-index, + hackage-security).

    Either way, given how you can now make repos exclusive in cabal.project, bringing this back should supercede the need for the generated .config files and not have any issues with newer revisions being added to upstream hackage.

  5. chreekat commented on Jan 22, 2026

    @chreekat
    MemberAuthor

    I'm keen to have good interop between cabal/stackage (and stack/hackage). I am not familiar with what it would take to create such a repo, but it certainly sounds like a good idea.

  6. chreekat commented on Jan 22, 2026

    @chreekat
    MemberAuthor

    Probably the best option would be to create an independent scheduled job, similar to the ones that update casa and the stackage website, e.g. stackage-update: https://github.com/haskellfoundation/hf-infrastructure/blob/main/stackage-builder/nixos-modules/stackage-server.nix#L196

  7. juhp commented on Jan 23, 2026

    @juhp
    Member

    TBH I don't think I ever heard of this stackage feature - at least I don't remember.
    Seems https://stackage-haddock.haskell.org/package-index/lts-13.30.tar.gz was the last one perhaps.

    It agree it could be useful - perhaps we can look at the code for more insight.
    There is also the (legacy) cabal.config files we still generate:
    eg https://www.stackage.org/lts-24.28/cabal.config
    (though I admit I always found them a bit clunky to use?).
    Dunno if it is worth converting them to cabal.project.freeze format?

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

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions