Commit 61137405 authored by Clint Adams's avatar Clint Adams

snap: Upgrading from 1.1.0.0 to 1.1.1.0

parent 464ffe5c
haskell-snap (1.1.1.0-1) unstable; urgency=medium
* New upstream version.
- Builds with current heist. closes: #897041.
-- Clint Adams <clint@debian.org> Mon, 28 May 2018 15:00:16 -0400
haskell-snap (1.1.0.0-3) unstable; urgency=medium
* Set Rules-Requires-Root to no.
......
......@@ -36,7 +36,7 @@ Build-Depends:
libghc-hashable-dev (<< 1.3),
libghc-hashable-dev (>= 1.2.0.6),
libghc-hashable-prof,
libghc-heist-dev (>= 1.0),
libghc-heist-dev (>= 1.1),
libghc-heist-dev (<< 1.2),
libghc-heist-prof,
libghc-lens-dev (>= 3.7.6),
......@@ -84,7 +84,7 @@ Build-Depends:
libghc-hunit-dev (>= 1.2.5.2),
libghc-hunit-dev (<< 1.7),
libghc-quickcheck2-dev (>= 2.4.2),
libghc-quickcheck2-dev (<< 2.11),
libghc-quickcheck2-dev (<< 2.12),
libghc-async-dev (>= 2.0.1.5),
libghc-async-dev (<< 2.3),
libghc-attoparsec-dev,
......
--- a/snap.cabal
+++ b/snap.cabal
@@ -103,7 +103,7 @@
Snap.Snaplet.Session.SecureCookie
build-depends:
- aeson >= 0.6 && < 1.3,
+ aeson >= 0.6 && < 1.4,
attoparsec >= 0.10 && < 0.14,
base >= 4 && < 4.11,
bytestring >= 0.9.1 && < 0.11,
@@ -119,16 +119,16 @@
-- snap does work with hashable 1.1.*, but some have complained that
-- the version disjunction causes problems with dependency resolution.
hashable >= 1.2.0.6 && < 1.3,
- heist >= 1.0 && < 1.1,
- lens >= 3.7.6 && < 4.16,
+ heist >= 1.0 && < 1.2,
+ lens >= 3.7.6 && < 4.17,
lifted-base >= 0.2 && < 0.3,
- map-syntax >= 0.2 && < 0.3,
+ map-syntax >= 0.2 && < 0.4,
monad-control >= 0.3 && < 1.1,
mtl >= 2.0 && < 2.3,
mwc-random >= 0.8 && < 0.14,
pwstore-fast >= 2.2 && < 2.5,
snap-core >= 1.0 && < 1.1,
- snap-server >= 1.0 && < 1.1,
+ snap-server >= 1.0 && < 1.2,
stm >= 2.2 && < 2.5,
text >= 0.11 && < 1.3,
time >= 1.1 && < 1.9,
@@ -220,7 +220,7 @@
build-depends:
aeson,
- async >= 2.0.1.5 && < 2.2,
+ async >= 2.0.1.5 && < 2.3,
attoparsec,
base,
bytestring,
rename-snap-binary
no-test-framework-smallcheck
tests-timeout
newer-deps
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment