hackage-server
hackage-server copied to clipboard
Hackage-Server: A Haskell Package Repository
https://hackage.haskell.org/package/toml-parser-2.0.1.2/reports/2 > Error: cabal: The program 'alex' version >=3.2 is required but it could not be found. https://hackage.haskell.org/package/toml-parser-2.0.1.2/toml-parser.cabal > build-tool-depends: > alex:alex >= 3.2,
Currently the documentation builder uses `cabal-install`'s v1 interfaces to drive the documentation build. This leads to awkward situation like #1388. @sclv previously attempted to migrate to v2-build but encountered resistance....
Currently, access tokens are scoped to the user account. I use these tokens to automate Hackage releases. For packages that I co-maintain with a group of people, I would strongly...
# summary Some cosmetic improvements Feel free to accept only a subset of the commits, they're very much all proposals. Sadly I cannot upload some of the pictures of the...
Just spent quite a bit of time trying to debug my `README.md` before working out that Candidate packages don't seem to have styles applied to code examples on the front...
I want to make a revision to `persistent-test` to bump a major version bound. When I do so, I get this output:  This warning is irrelevant to the job...
Hackage shows deprecated and preferred versions on each package page, but it seems to combine the two types of version ranges in the package index. This means that cabal can't...
Deprecation is a subtle mechanism. In particular, deprecated versions can still be picked by the solver --- to most people's surprise. It has been brought up many times (e.g. https://github.com/haskell/hackage-server/issues/1345)....
@phadej and @gbaz suggested removing preferred versions in #1345, so I'm opening a new issue to discuss whether the feature is still needed. Is there a use case for preferring...
Given that this is dynamic and hopefully cheap-to-generate I think we should prohibit the CDN from caching this endpoint. With the status quo one can be very easily confused by...