Skip to content

conflict between /home/runner/.cabal and /home/runner/.config/cabal/config #108

@tych0

Description

@tych0

Hi, I am seeing failures like:

2025-01-02T20:34:19.0988675Z flock xcffib.cabal cabal --config-file=./cabal.config new-run --minimize-conflict-set -j4 exe:xcffibgen -- --input ./proto/src --output ./xcffib
2025-01-02T20:34:19.1249266Z Warning: Both /home/runner/.cabal and /home/runner/.config/cabal/config exist
2025-01-02T20:34:19.1249706Z - ignoring the former.
2025-01-02T20:34:19.1250062Z It is advisable to remove one of them. In that case, we will use the remaining
2025-01-02T20:34:19.1250489Z one by default (unless '$CABAL_DIR' is explicitly set).
2025-01-02T20:34:19.6802799Z Warning: The package list for 'hackage.haskell.org' does not exist. Run 'cabal
2025-01-02T20:34:19.6803760Z update' to download it.
2025-01-02T20:34:19.6951914Z Resolving dependencies...
2025-01-02T20:34:19.6958135Z Error: [Cabal-7107]
2025-01-02T20:34:19.6958565Z Could not resolve dependencies:
2025-01-02T20:34:19.6959032Z [__0] trying: xcffib-1.6.0 (user goal)
2025-01-02T20:34:19.6959619Z [__1] unknown package: optparse-applicative (dependency of xcffib)
2025-01-02T20:34:19.6960341Z [__1] fail (backjumping, conflict set: optparse-applicative, xcffib)
2025-01-02T20:34:19.6961443Z After searching the rest of the dependency tree exhaustively, these were the goals I've had most trouble fulfilling: xcffib, optparse-applicative

but only sometimes, and only when the warning about /home/runner/.cabal and /home/runner/.config/cabal/config is printed.

Seems like the action sets up one of these directories and updates the hackage cache there, butthat only causes problems in some cases? Unclear exactly what's going on to me.

Full actions run here:

https://github.com/tych0/xcffib/actions/runs/12613197315/job/35150752203

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions