Without adding "allow-newer" for the package "base," I get the build failure
```
Configuring darcs-2.12.0...
clang: warning: -Wl,-headerpad_max_install_names: 'linker' input unused
clang: warning: argument unused during compilation: '-L/usr/local/lib'
clang: warning: argument unused during compilation:
'-L/System/Library/Frameworks/OpenGL.framework/Versions/Current/Libraries'
checking whether to use -liconv...
dist/dist-sandbox-296ea86f/setup/setup.hs:149:15-41: Irrefutable pattern
failed for pattern Just lib
cabal: Leaving directory '.'
cabal: Error: some packages failed to install:
darcs-2.12.0 failed during the configure step. The exception was:
ExitFailure 1
```
Can be removed as soon as upstream bumps the base version, assuming the same
problem doesn't affect any of the dependencies at that time.
Closes#1442.
Signed-off-by: ilovezfs <ilovezfs@icloud.com>
Without adding "allow-newer" for the packages base and transformers, I
get build failures like the following:
```
clang: warning: argument unused during compilation: '-L/System/Library/Frameworks/OpenGL.framework/Versions/Current/Libraries'
Resolving dependencies...
cabal: Could not resolve dependencies:
trying: stack-1.1.2 (user goal)
trying: base-4.9.0.0/installed-4.9... (dependency of stack-1.1.2)
trying: transformers-0.5.2.0/installed-0.5... (dependency of stack-1.1.2)
next goal: retry (dependency of stack-1.1.2)
rejecting: retry-0.7.2 (conflict: base => ghc-prim==0.5.0.0/installed-0.5...,
retry => ghc-prim<0.5)
etc. etc.
```
Can be removed as soon as the dependencies setting unecessary
restrictions on these versions catch up, or as soon as stack itself has
a similar built-in workaround.
Closes#1411.
Signed-off-by: ilovezfs <ilovezfs@icloud.com>
Without adding "allow-newer" for the packages aeson, base, HTTP, time,
and transformers, I get build failures like the following (depends which
subset you're trying):
```
Resolving dependencies...
cabal: Could not resolve dependencies:
trying: elm-compiler-0.17 (user goal)
trying: base-4.9.0.0/installed-4.9... (dependency of elm-compiler-0.17)
trying: unix-2.7.2.0/installed-2.7... (dependency of
process-1.4.2.0/installed-1.4...)
next goal: aeson (dependency of elm-compiler-0.17)
rejecting: aeson-0.11.2.0, aeson-0.11.1.4, aeson-0.11.1.3, aeson-0.11.1.2,
aeson-0.11.1.1, aeson-0.11.1.0, aeson-0.11.0.0, aeson-0.9.0.1, aeson-0.9.0.0
(conflict: elm-compiler => aeson>=0.7 && <0.9)
rejecting: aeson-0.8.1.1, aeson-0.8.1.0, aeson-0.8.0.2 (conflict:
base==4.9.0.0/installed-4.9..., aeson => base>=4.5 && <4.9)
rejecting: aeson-0.7.0.6, aeson-0.7.0.4 (conflict: unix =>
etc. etc.
```
Can be removed as soon as the dependencies setting unecessary
restrictions on these versions catch up, or as soon as elm itself has a
similar built-in workaround.
Closes#1409.
Signed-off-by: ilovezfs <ilovezfs@icloud.com>
All of the changes needed have been accepted upstream.
For additional details, see the upstream report here:
http://git-annex.branchable.com/bugs/ghc_8.0.1_build_fixes
Fix "Couldn't match expected type 't' with actual type ...":
fe944a96d3
Also, upstream added a cabal.config to "allow-newer" for the packages "base,"
"time," and "transformers," primarily to work around a strict depedency issues
with the aws package, which just needs to bump the versions:
7b61c7f5d0
This is applied by installing the new cabal.config file as a resource rather
than using a patch, since the patch does not apply cleanly due to prior
unrelated changes in git-annex.cabal.
Bump base from < 4.9 to < 5.0:
f8e71e1a52
We don't need to do this explicitly in the formula because the cabal.config
mentioned above already has this effect.
Closes#1407.
Signed-off-by: ilovezfs <ilovezfs@icloud.com>
* Switch to using a versioned release for devel rather than one which moves
around constantly. We're trying to move in this direction because the end goal
is to bottle devel as well, which we can't do if those can move around.
* Fix the dylib vanilla symlinking to work for stable/devel.
Closes#1274.