From e9e81da19fb99a8184d5df18518adf5e06fce1fe Mon Sep 17 00:00:00 2001 From: Jens Petersen Date: Tue, 4 Oct 2016 11:56:23 +0900 Subject: [PATCH] Revert "drop bound for terminal-progress-bar (#1857)" since 0.1.[01] fails to test/build (roelvandijk/terminal-progress-bar#12) This reverts commit 909538ef4694ee8bd9be2bb7292f613bf3c8c43e. --- build-constraints.yaml | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/build-constraints.yaml b/build-constraints.yaml index 418e5bde..81e30073 100644 --- a/build-constraints.yaml +++ b/build-constraints.yaml @@ -2558,6 +2558,9 @@ packages: # https://github.com/fpco/stackage/issues/1842 - dependent-sum < 0.4 + # https://github.com/fpco/stackage/issues/1857 + - terminal-progress-bar < 0.1.0 # Re-enable tests when lifting this + # https://github.com/fpco/stackage/issues/1863 - newtype-generics < 0.4 # May need to disable test suite when lifting this https://github.com/jcristovao/newtype-generics/issues/7 - MemoTrie < 0.6.5 @@ -2725,7 +2728,7 @@ skipped-tests: # Blocked by stackage upper bounds. These can be re-enabled once # the relevant stackage upper bound is lifted. - + - terminal-progress-bar # Fixed in 0.1.0 https://github.com/roelvandijk/terminal-progress-bar/issues/11 # Runtime issues - blank-canvas # Never finishes https://github.com/ku-fpg/blank-canvas/issues/73