Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix stackage#4312: Relax network version bound. #10

Merged
merged 2 commits into from
Jan 29, 2019

Conversation

naushadh
Copy link
Owner

Issue: commercialhaskell/stackage#4312

Should be safe for us to relax bound as upstream `mysql-haskell` library has already safely relaxed its bound.

Tested with the following `stack.yaml`:

```yaml
resolver: lts-10.4
packages:
  - ./persistent
  - ./persistent-template
  - ./persistent-sqlite
  - ./persistent-test
  - ./persistent-mongoDB
  - ./persistent-mysql
  - ./persistent-mysql-haskell
  - ./persistent-postgresql
  - ./persistent-redis
  - ./persistent-qq
extra-deps:
- monad-logger-0.3.28.1
- mysql-simple-0.4.4

- mono-traversable-1.0.8.1
- unliftio-0.2.4.0
- unliftio-core-0.1.1.0
- async-2.1.1.1
- typed-process-0.2.1.0
- resourcet-1.1.11

- network-3.0.0.0
# - network-2.6.3.6
- tcp-streams-1.0.1.1
- io-streams-1.5.1.0
- mysql-haskell-0.8.4.2
```
@naushadh naushadh merged commit 5b9f487 into persistent-mysql-haskell Jan 29, 2019
@@ -42,7 +42,7 @@ library
-- keep the following in sync with @mysql-haskell@ .cabal
, io-streams >= 1.2 && < 2.0
, time >= 1.5.0
, network >= 2.3 && < 3.0
, network >= 2.3 && < 4.0
Copy link

@hvr hvr Jan 29, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Note that network follows the PVP and not SemVer and therefore this upper bound makes no sense; see also https://pvp.haskell.org/faq/#how-does-the-pvp-relate-to-semantic-versioning-semver

IOW, the proper upper bounds for such packages (see also io-streams above) is

build-depends: network (>= 2.3 && < 2.9) ||  (>= 3 && < 3.1)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants