i3status-rust, docker-compose: each module declares the packages it needs (issue 628) #271

Closed
mesh-admin wants to merge 2 commits from fix/628-modules-declare-every-package-they-need into main
2 Commits
Author SHA1 Message Date
mesh-admin ea73e713f5 i3status-rust: name the pacman-contrib package apart from the update script, and expect it in the test (issue 628)
mesh/merge-gate out of date: judged against trunk cd239283207a, the trunk is now 0d723484a84a; judged again on a recheck or when it is merged
mesh/repo-check out of date: judged against trunk cd239283207a, the trunk is now 0d723484a84a; judged again on a recheck or when it is merged
mesh/delivery closed: the pull request closed unmerged
mesh/check failed: shanks: novox/mesh-catalog#271 does not merge into the trunk: files in conflict: modules/i3status-rust/README.md | ea73e713f503 on …
The package took the id `updates`, which the update script already holds, so the node-engine refused two resources with one identity.
2026-10-13 11:59:31 +00:00
mesh-admin e79197d5a1 i3status-rust, docker-compose: each module declares the packages it needs (issue 628)
mesh/merge-gate out of date: judged against trunk 19ecad261cf2, the trunk is now 8922c890595b; judged again on a recheck or when it is merged
mesh/repo-check out of date: judged against trunk 19ecad261cf2, the trunk is now 8922c890595b; judged again on a recheck or when it is merged
mesh/delivery superseded: a newer head of the same pull request
i3status-rust left pacman-contrib to the pacman module because two modules declaring one package was once refused; ADR 0303 allows it, so the bar declares what its update block runs. docker-compose's README said the package goes with the module, which the node-engine never does.
2026-10-13 11:52:38 +00:00