Stackage: megaparsec-7 and hspec-megaparsec-2

Created on 5 Sep 2018  路  23Comments  路  Source: commercialhaskell/stackage

hspec-megaparsec-2.0.0 (Mark Karpov markkarpov92@gmail.com @mrkkrp) is out of bounds for:

  • [ ] dotenv-0.5.2.5 (>=1.0 && < 2.0). Stack Builders [email protected] @stackbuilders. @cmotoche @javcasas @jsl @juanpaucar @sestrella. Used by: test-suite
  • [ ] inflections-0.4.0.3 (>=1.0 && < 2.0). Stack Builders [email protected] @stackbuilders. @cmotoche @javcasas @jsl @juanpaucar @sestrella. Used by: test-suite

megaparsec-7.0.1 (Mark Karpov markkarpov92@gmail.com @mrkkrp) is out of bounds for:

  • [ ] config-ini-0.2.2.0 (==6.*). No maintainer. @aisamanra. Used by: library
  • [ ] dhall-1.16.1 (>=6.1.1 && < 6.6). Gabriel Gonzalez Gabriel439@gmail.com @Gabriel439. @dhall-lang. Used by: library
  • [ ] dotenv-0.5.2.5 (>=6.0 && < 7.0). Stack Builders [email protected] @stackbuilders. @cmotoche @javcasas @jsl @juanpaucar @sestrella. Used by: library, executable, test-suite
  • [ ] inflections-0.4.0.3 (>=6.0 && < 7.0). Stack Builders [email protected] @stackbuilders. @cmotoche @javcasas @jsl @juanpaucar @sestrella. Used by: library, test-suite
  • [ ] require-0.4.0 (>=6.5.0 && < 7). Nikita Tchayka nikitatchayka@gmail.com @nickseagull. @theam. Used by: library, executable, test-suite, benchmark
  • [ ] servant-dhall-0.1.0.1 (>=6.5.0 && < 6.6). Oleg Grenrus oleg.grenrus@iki.fi @phadej. @jkarni @phadej. Used by: library
  • [ ] tomland-0.4.0 (>=6.5.0 && < 6.6.0). Kowainik xrom.xkov@gmail.com @ChShersh. @kowainik. Used by: library
bounds

All 23 comments

New versions (compatible with megaparsec-7.0.0 & hspec-megaparsec-2.0.0) have been released:

  • modern-uri-0.3.0.0
  • stache-2.0.0
  • cue-sheet-2.0.0

I'll get to MMark stuff a bit later.

  • mmark-0.0.6.0 released, it's compatible with Megaparsec 7
  • mmark-ext-0.2.1.0 has been updated in revision 2 to allow modern-uri-0.3.0.0
  • mmark-cli-0.0.4.0 released, it's compatible with Megaparsec 7 and mmark-0.0.6.0

version-3.5.0 released to match.

I've updated the initial description.

Updated list:

megaparsec-7.0.1 (Mark Karpov markkarpov92@gmail.com @mrkkrp) is out of bounds for:

  • [ ] dotenv-0.5.2.5 (>=6.0 && < 7.0). Stack Builders [email protected] @stackbuilders. @cmotoche @javcasas @jsl @juanpaucar @sestrella. Used by: library, executable
  • [ ] inflections-0.4.0.3 (>=6.0 && < 7.0). Stack Builders [email protected] @stackbuilders. @cmotoche @javcasas @jsl @juanpaucar @sestrella. Used by: library
  • [ ] tomland-0.4.0 (>=6.5.0 && < 6.6.0). Kowainik xrom.xkov@gmail.com @ChShersh. @kowainik. Used by: library

Hey! What would be the fix for this? Setting the lower bound to the version specified?

megaparsec 7 changed its API in a way that just about every user package is going to have to adapt to, so it's probably not a simple bounds bump. There's stackbuilders/inflections-hs#60 blocking this issue, but it looks like the maintainers of that package are waiting for this issue to be resolved before they merge, so apparently we're deadlocked...

@NickSeagull here's the fix I had to do for versions: https://gitlab.com/fosskers/versions/commit/9de04ad00aac47020462e465fa59485579f24f12

The megaparsec CHANGELOG is also a good place to double-check.

dotenv-0.6.0.1 and inflections-0.4.0.4 support megaparsec-7.0.1 and hspec-megaparsec-2.0.0

Here's an updated list now:

megaparsec-7.0.1 (Mark Karpov markkarpov92@gmail.com @mrkkrp) is out of bounds for:

  • [ ] tomland-0.4.0 (>=6.5.0 && < 6.6.0). Kowainik xrom.xkov@gmail.com @ChShersh. @kowainik. Used by: library

process-1.6.3.0 is out of bounds for:

  • [x] dotenv-0.6.0.1 (>=1.6.4.0 && < 1.7). Stack Builders [email protected] @stackbuilders. @cmotoche @javcasas @jsl @juanpaucar @sestrella. Used by: library, executable

I am going to have to set upper bounds for both dotenv and inflections in the meantime.

@alexeyzab I can update the bounds for dotenv to use process-1.6.3.0. I saw the API of process hasn't changed.

@alexeyzab I changed the boundaries of process to process-1.6.3.0 in dotenv-0.6.0.2

@CristhianMotoche Great, thanks!

Added to the list above:

  • tomland-0.4.0 (>=6.5.0 && < 6.6.0). Kowainik xrom.xkov@gmail.com @ChShersh. @kowainik. Used by: library

@DanBurton Sorry for being late for the party :pray: I'm planning to release tomland-0.5.0 with constraints megaparsec >= 7.0 && < 7.1 in nearest couple days (after Hacktoberfest is over).

The list as currently reported by stackage-curator:

megaparsec-7.0.3 is out of bounds for:

  • confcrypt-0.1.0.3 (==6.5.*). Chris Coffey chris@foldl.io @ChrisCoffey. @https:. Used by: library, executable, test-suite
  • dotenv-0.5.2.5 (>=6.0 && < 7.0). Stack Builders [email protected] @stackbuilders. @CristhianMotoche @javcasas @jsl @juanpaucar @sestrella. Used by: library, executable
  • inflections-0.4.0.3 (>=6.0 && < 7.0). Stack Builders [email protected] @stackbuilders. @CristhianMotoche @javcasas @jsl @juanpaucar @sestrella. Used by: library
  • tomland-0.4.0 (>=6.5.0 && < 6.6.0). Kowainik xrom.xkov@gmail.com @ChShersh. @kowainik. Used by: library

Hi @DanBurton, it's not clear to me why dotenv and inflections keep being marked as out of bounds. I mention this because versions with proper boundaries to solve this, are already on hackage.

  • dotenv has support for megaparsec >=7.0.1 , starting from version 0.6.0.1
  • inflections, starting from version 0.4.04

@juanpaucar my mistake!

They are constrained here, which I did not notice:
https://github.com/commercialhaskell/stackage/blob/83080d236aa0effd6d64823665659b8628578930/build-constraints.yaml#L2018

Normally we would constrain them here:
https://github.com/commercialhaskell/stackage/blob/83080d236aa0effd6d64823665659b8628578930/build-constraints.yaml#L4308

No further action is needed on your part, @juanpaucar.

Thanks @DanBurton, I thought I was missing something and I didn't want to stop you folks from upgrading megaparsec :)

Thanks for letting me know @DanBurton. I just pushed an update to use the newer 7.0.x megaparsec api.

@DanBurton sorry for the delay. tomland-0.5.0 has been released to Hackage with megaparsec ^>= 7.0.1 bounds.

@ChShersh thanks! I've opened a PR (https://github.com/commercialhaskell/stackage/pull/4126) to restore tomland to stackage; it was temporarily removed to unblock megaparsec.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

asr picture asr  路  7Comments

snoyberg picture snoyberg  路  8Comments

erikd picture erikd  路  6Comments

bergmark picture bergmark  路  3Comments

DanBurton picture DanBurton  路  7Comments