Re-enable LambdaHack (LambdaHack/LambdaHack#300).

[alaendle]

Checklist:

• Meaningful commit message, eg add my-cool-package (please don't mention build-constraints.yml)
• [ x At least 30 minutes have passed since uploading to Hackage
• If applicable, required system libraries are added to 02-apt-get-install.sh or 03-custom-install.sh
• (optional) Package is compatible with the latest version of all dependencies (Run cabal update && cabal outdated)
• (optional) Package have been verified to work with the latest nightly snapshot, e.g by running the verify-package script

The script runs virtually the following commands in a clean directory:

  stack unpack $package-$version # `-$version` is optional
  cd $package-$version
  rm -f stack.yaml && stack init --resolver nightly --ignore-subdirs
  stack build --resolver nightly --haddock --test --bench --no-run-benchmarks

[Mikolaj]

I think that should make package Allure legit again. In any case, thank you very much!

[alaendle]

@Mikolaj - Allure will get re-enabled semi-automatically later - since the only constraint that holds it back is the currently missing LambdaHack - so as soon as LamdaHack is in nightly this should unblock Allure.

stackage/build-constraints.yaml

Line 6065 in 8a0a778

- Allure < 0 # tried Allure-0.11.0.0, but its *library* requires the disabled package: LambdaHack