Skip to content

miso update: actually update the package list - #28

Merged
dmjio merged 1 commit into
mainfrom
update-package-list
Oct 23, 2026
Merged

dmjio merged 1 commit into
mainfrom
update-package-list

Conversation

@dmjio

@dmjio dmjio commented Oct 23, 2026

Copy link
Copy Markdown
Member

The bug: miso update printed "Updating the package list", but versions never moved.

Why:

  1. The child miso mcabal update reset CABALDIR from the project it ran in (via the inherited MISO_PROJECT).
  2. So the new Stackage list was written to the project's .miso/mcabal.
  3. The old shared list in $MISO_HOME/mcabal was then copied back over it.

The fix: the update now runs in $MISO_HOME/mcabal with MISO_PROJECT cleared, so the child writes the shared list.

Checked with the built tool and a stand-in curl serving a snapshot with split 9.9.9, starting from a shared list with split 0.1.0:

  • Before: both lists still had 0.1.0, and the snapshot was downloaded into the project's .miso/.
  • After: both lists have 9.9.9, downloaded into $MISO_HOME/mcabal.

Stackage itself isn't reachable from where I tested, so this PR's CI and a real miso update are the end-to-end check.


Generated by Claude Code

miso update ran "miso mcabal update" with CABALDIR set to $MISO_HOME/mcabal,
but the child set CABALDIR again from the project it ran in (MISO_PROJECT,
which this process had set).  So the new Stackage list went to the
project's .miso/mcabal, the old shared list was then copied back over it,
and versions never moved, while it said "Updating the package list".

The update now runs in $MISO_HOME/mcabal with MISO_PROJECT cleared, so the
child uses the shared list.

Checked with the built tool and a stand-in curl that serves a snapshot
with split 9.9.9 (the shared list had split 0.1.0): before, both lists
still had 0.1.0 and the snapshot was downloaded into the project's .miso/;
now both have 9.9.9, downloaded into $MISO_HOME/mcabal.
@dmjio
dmjio merged commit d4ab258 into main Oct 23, 2026
8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant