Compatibility with aeson-2.0 about yaml HOT 9 CLOSED

It would indeed be nice if a aeson < 2 constraint could be added to the existing versions since yaml is a pretty widely-used package and currently it's very easy to run into install plans that have no chance of building.

from yaml.

I think it might be sufficient to revise v0.8.5.3 and up.

And for reference: #202 contains a compatibility fix for this issue.

from yaml.

I'm running into this while trying to install various tools e.g. hpack or prune-juice.

For others who stumble across this, a temporary workaround is cabal install PACKAGE --constraint='aeson<2'.

from yaml.

@mouse07410 I have added some bounds for the packages you mentioned. If you run into more issues of this kind, please raise an issue on the issue tracker of the relevant package. Feel free to ping me if the package maintainers don't resolve the issue themselves.

from yaml.

Actually --allow-newer isn't even necessary to produce the error, since most yaml versions on Hackage don't have upper bounds on aeson.

from yaml.

As a Hackage trustee, I've pushed some Hackage revisions that should prevent yaml from futilely building with aeson >= 2.

If you run into similar errors with other packages, feel free to ping me or raise an issue at https://github.com/haskell-infra/hackage-trustees/issues.

from yaml.

@sjakobi I'm quite a novice, but it looks like with the current yaml-0.11.6.0 and its dependencies (aeson is probably the culprit), a lot of popular packages fail to build (tried GHC-9.0.1 , 8.10.7, 8.8.4, 8.6.5; cabal-3.6.2.0):

• hoogle
• hindent
• hlint
• hpack
• can't recall others, but pretty sure I hit more than the above...

The above workaround appears effective, thanks! Is there a way to (temporarily) enforce it via global Cabal config file, e.g., ~/.cabal/config or such?

from yaml.

See #202

from yaml.

As a Hackage trustee, I've pushed some Hackage revisions that should prevent yaml from futilely building with aeson >= 2.

Me too. Some releases in the range >= 0.8.5.3 and <= 0.8.8.2 were still missing the bound aeson < 2.

from yaml.