Right, there's no evidence of use of mirrors because afaik it cannot be configured. And normal verbosity doesn't print anything about it. But it is, in fact, something cabal uses.
I know this information doesn't help. :(
Last week I had to fix the generation of all-cabal-hashes, which was failing because it relied on the fpco mirror. Next week I'll continue pushing for fixing the mirror situation, itself.
Until the mirror situation gets resolved, the only thing I can think of for you to try is to figure out why Hackage can't serve you directly. Maybe fork the Haskell setup action and add some extra verbosity? Are you on private runners? Is there network weirdness? Is the CDN treating you as a threat?
This mailing list is not as active as Discourse.. maybe post there to try to find others with the same problem?
I know you said stop using mirrors.
I just made the CI job prints its $HOME/.cabal/config and this was in it:
I don't see any evidence that Cabal is configured to use mirrors. Could this redirection be happening on the Hackage side?
Ivan
On Fri, Aug 14, 2026 at 08:28:44AM -0700, Ivan Perez wrote:
> I'm using https://github.com/haskell-actions/setup to set up Haskell.
>
> I doubt I'm the only person affected by this.
>
> Is that something that could / should be adjusted there so that it helps
> everyone?
I think regardless of the cause or solution, if you're seeing it in
haskell-actions/setup then you should file an issue there:
https://github.com/haskell-actions/setup/issues/new
_______________________________________________
Haskell-Cafe mailing list -- haskell-cafe@haskell.org
To (un)subscribe, modify options or view archives go to:
Only members subscribed via the mailman list are allowed to post.
_______________________________________________
Haskell-Cafe mailing list -- haskell-cafe@haskell.org
To (un)subscribe, modify options or view archives go to:
Only members subscribed via the mailman list are allowed to post.