This repository has been archived by the owner on Jan 5, 2024. It is now read-only.
Investigate why 'cabal update' hasn't run properly when setting up GHC 8.2 and cabal 2.4 #158
Comments
andreasabel
added a commit
that referenced
this issue
Jan 10, 2023
This commit introduces a new boolean input `cabal-update` that defaults to `true`. If set to `false`, the `cabal update` step will be skipped. The new flag `cabal-update` is proper boolean, it only accepts the YAML 1.2 truth values `true` and `false` (also in captial and uppercase). This is contrast to other "boolean" flags that are "unset" by default and can be "set" with any non-empty string. To test that `cabal update` happens, this commit also introduces a new Haskell test project into CI that depends on a common Hackage package (`base-orphans`). Original commits: * Fix #29: new input 'cabal-update: false' to turn off 'cabal update' * Test 'cabal-update: false' * README: Add 'cabal-update' to table of inputs * Accept YAML 1.2 booleans as values for 'cabal-update' * CI: test 'cabal-update: true': project with Hackage dependency * Default value for 'cabal-update' * CI: use cabal_update (underscore) in matrix * Fixup: project with Hackage dependency * Work around #158 * Extra clarification of boolean vs "boolean" inputs
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
This test:
actions/.github/workflows/workflow.yml
Lines 45 to 47 in ed06300
does
/home/runner/.ghcup/bin/cabal update(under Setting up cabal) but it seems to not affectcabal build. Maybe there are two conflictingcabals in the PATH with different.cabaldirs?CI run: https://github.com/haskell/actions/actions/runs/3851999748/jobs/6563739708#step:3:172
Log: 13_GHC 8.2.2, Cabal 2.4.1.0 - ubuntu-latest.txt
The text was updated successfully, but these errors were encountered: