doctest-0.12.0 (Simon Hengel sol@typeful.net @sol) is out of bounds for:
FYI, there is no accompanying upper bound commit linked because we're trying to remove them all for the upcoming GHC-8.2.1 release (work in progress over at https://github.com/fpco/stackage/commit/5cdd7df62943ae662a2433b3385dd6669928ebd1).
I'll update the Kmettiverse packages once there's a resolution on https://github.com/phadej/cabal-doctest/issues/19.
Fixed in pipes-group-1.0.7 and turtle-1.4.0
An update: I've uploaded versions of the following packages to Hackage that support doctest-0.12:
adbitsboundbytescomonaddistributiveintervalslens-aesonlinearlinear-acceleratelog-domainsemigroupoidszippersThat is, every Kmettiverse package except lens. I've decided not to upload a new version of lens yet since there have been some difficulties upgrading lens to doctest-0.12 which haven't been fully resolved yet: https://github.com/ekmett/lens/issues/756
Fixed for servant-ruby with 0.3.0.0.
@bergmark I deprecated 0.12.0 on Hackage. I recommend that you use < 0.12.0 for Stackage until https://github.com/sol/doctest/issues/170 is resolved. There will be a 0.13.0 release later on.
@sol is it possible to release a fix in the 0.12.x series? It would save maintainers some, or in Ryan's case a lot of, effort :)
@bergmark 0.13.0 will introduce a breaking change vs. 0.12.0 so it has to be a major version bump. I'm sorry if that causes additional work for anybody.
Upgrading to 0.13 will be significantly easier for me, luckily. For 0.12, I had to release new versions of each package to work around an unrelated problem in the way we were using cabal-doctest, but from now on I can manage with simple Hackage revisions.
@bergmark To clarify, there is no workaround for this bug, as it is a GHC bug. The only way I'm aware of to prevent it is to change the behavior of doctest in a backward-incompatible manner.
doctest-0.13.0 is on Hackage.
All of the packages in https://github.com/fpco/stackage/issues/2663#issuecomment-318880588, as well as lens, now support doctest-0.13.
Since I'm pretty new around here: do I need to send a PR for unblocking myself or does that magically happen?
@Porges A PR to unblock is much more reliable, I'd definitely recommend it.