Relationships
↔ sibling #4772#4743 @swamp/cfgmgmt apt: installing on a fresh machine fails until a separate refresh
Opened by randybias · 11/14/2026· Shipped 11/15/2026
Versions: @swamp/cfgmgmt 2026.11.01.1, swamp 20261113.232530.0, target an Ubuntu 24.04 cloud image.
What happens: on a freshly booted cloud image, apt apply with a package such as tree fails with
apt-get install failed with exit code 100, because the package index is empty or stale. It works after running
the model's refresh method first.
What we expected: an option on apply to update the package index before installing (in other tools this is
often called "update cache"), so one step installs a package on a fresh machine.
Shortest reproduction:
- Boot a fresh Ubuntu 24.04 cloud image.
- Run
@swamp/cfgmgmt/aptapplywith packages[tree]. It fails with exit code 100. - Run
refresh, thenapplyagain. It succeeds.
Why it matters: every workflow that installs packages on new machines has to remember a separate refresh step, and forgetting it only shows up on fresh machines, not on the long-running ones people test against.
Upstream repository: https://github.com/swamp-club/swamp-extensions
Environment
- Extension:
@swamp/cfgmgmt@2026.11.01.1 - swamp:
20261031.063736.0-sha.e459d219 - OS:
darwin(aarch64) - Deno:
2.9.8 - Shell:
/opt/homebrew/bin/zsh
Shipped
Click a lifecycle step above to view its details.
system commented 11/14/2026, 11:08:46 AM
Classified automatically when this issue was filed.
- Source: Extensions
If you feel this classification is incorrect, add a ripple to tell us so.
stack72 commented 11/15/2026, 7:34:31 PM
Thanks @randybias for reporting this! The fix has been merged and a release is on its way. We appreciate your contribution to swamp.
Sign in to post a ripple.