Revert "stack.yaml: Update to lts-19.33 and aws-0.24"
This reverts commit 648e59cac2
.
Failed to build on windows, because
In the dependencies for haskeline-0.8.2:
Win32-2.11.1.0 from Stack configuration does not match >=2.1 && <2.10 || >=2.12 (latest
matching version is 2.13.4.0)
jkniiv did find a solution that builds:
-- Win32-2.11.1.0
+- Win32-2.9.0.0
+- Cabal-3.6.3.0
+- directory-1.3.7.1
+- process-1.6.17.0
+- time-1.11.1.2
But that is a quite old version of Win32 and risks bugs from it, and bumping
Cabal and directory to newer than lts-19.33 has seems also likely to be risky.
So, I've given up. aws-0.24 won't be able to be in the stack build until
there's a stackage lts (or nightly) that has filepath (>=1.4.100.0),
which will not happen until sometime after the next ghc release.
This commit is contained in:
parent
326f01f5a3
commit
8f2829e646
4 changed files with 26 additions and 7 deletions
|
@ -422,3 +422,5 @@ Git Annex is great. I use it several times a week with my multigigabyte backups,
|
|||
|
||||
[[!meta author=jkniiv]]
|
||||
[[!meta title="windows: Resolver lts-19.33 still (!) causes trouble with Win32 for stack builds"]]
|
||||
|
||||
> [[fixed|done]] --[[Joey]]
|
||||
|
|
|
@ -0,0 +1,17 @@
|
|||
[[!comment format=mdwn
|
||||
username="joey"
|
||||
subject="""comment 1"""
|
||||
date="2023-02-20T19:12:19Z"
|
||||
content="""
|
||||
Drat. The problem is haskeline-0.8.2 depending on a different Win32
|
||||
version. I'll take your word for it that was the only dependency solution
|
||||
though.
|
||||
|
||||
Win32-2.9.0.0 is quite old and I don't want to risk reverting to some bug
|
||||
fixed in the meantime. And I'm doubtful about bumping Cabal and directory
|
||||
to newer versions too.
|
||||
|
||||
So, I've reverted this attempt, and won't make another one until there's a
|
||||
ghc release that has the filepath (>=1.4.100.0) that Wind32 needs.
|
||||
Shouldn't be more than half a year or so..
|
||||
"""]]
|
Loading…
Add table
Add a link
Reference in a new issue