Mention which `file+noindex` repository ignores TIMESTAMP

Open Beginner friendly
#12,638 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 3 days

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
72/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
haskell
Domain
build-system

Research direction

Search cabal-install for the exact warning text shown, index-state ignored for file+noindex repositories; that should lead to the repository/index-state validation path. Read how repository stanzas are parsed so the stanza name is available where the warning is built, then revise the message and reproduce with a minimal cabal.project containing two file+noindex repositories and cabal build --dry-run. Done when both warnings name their repository; run the cabal-install config warning tests if present.

Written by the indexing model from the issue text.

Description

needs triage type: enhancement

Can we mention which file+noindex repository ignores or doesn't apply an --index-state=TIMESTAMP? We can have more than one such repository and the message duplicates itself without saying more.

Current Behaviour
$ cat cabal.project
packages: .
repository local-a
  url: file+noindex:///path/to/repoA
repository local-b
  url: file+noindex:///path/to/repoB
index-state: 2026-06-01T00:00:00Z

$ cabal build --dry-run
Warning: index-state ignored for file+noindex repositories
Warning: index-state ignored for file+noindex repositories
Resolving dependencies...
...
Better Behaviour

Would be something like:

Warning: index-state ignored for file+noindex repository 'local-a'
Warning: index-state ignored for file+noindex repository 'local-b'
Dominant language
Haskell
Stars
1.8k
Forks
766
Avg merge
5d 21h
Merged PRs (30d)
27

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from haskell/cabal

All issues in haskell/cabal

Similar issues

More Haskell issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.