8 Commits

Include renames

Author	SHA1	Message	Date
jschoubben	2b495c4818	pacman keeps one mirror list for the mesh, ranked in the write that opens each round and written by every node (ADR 0585, issue 1876) ... Each node's reflector ranked its own list on its own timer, and on 2026-10-31 one node's lagging first mirror left it a Node.js version behind the rest. The list is now the module's state mirrors, key list: the node that opens a week's round ranks it with the module's reflector options, keeps only mirrors whose last sync is no older than the newest found, and the round's key names the list's revision. Every keeper writes /etc/pacman.d/mirrorlist whole from the key through the root helper's new verb mirrorlist, when the key changes and when the file differs, and never writes an empty or unreadable list. reflector.timer is declared stopped and disabled, and reflector.conf saves nothing. pacman_mirrors answers the shared list, its ranker and age and whether this node's file matches; with refresh it asks this node's keeper to rank again, refused while a round runs, naming it. The round's integration test proves the opening write and both nodes' files. Claude-Session: https://claude.ai/code/session_01NcbgfJ9Gum47zkFKWRaovL	2026-11-01 16:18:22 +01:00
jschoubben	f8ac498d64	issue 1841/S11: judge the upgrades' health from the runs, rounds and held kernels on the bus, so a node that slept through a run is judged by what happened, not by a unit's age (folds issue 1579)	2026-10-22 17:38:08 +02:00
jschoubben	32c66a98c1	Merge branch 'feat/upgrade-safety' into p2	2026-10-22 14:36:14 +02:00
jschoubben	62437f8964	issue 1840/S8: answer the package view from the bus, so every node is read at once and none is asked ... pacman_packages answers one package on every node, or each node's counts, its explicit packages no module declares and its foreign ones apart, the versions that differ and the packages on some nodes only, with a node over the bus's cap marked not current. pacman_updates, pacman_installed and pacman_foreign read the keeper's states instead of the machine; pacman_updates says when each node's list last changed.	2026-10-22 14:36:11 +02:00
jschoubben	95e69276c3	Carry out an upgrade as an ask its node's keeper takes, through the root helper, and follow a run to its end after a restart, so a hand upgrade is a recorded, checked run like any other (issue 1841/S5)	2026-10-22 14:35:19 +02:00
mesh-tools	bd10ec4f0d	Say a weekly upgrade that hangs past two hours, so a stuck pacman lock is loud (issue 1574, ADR 0477)	2026-10-21 08:08:04 +00:00
mesh-tools	e3ac017c28	Test the weekly upgrade's timer and its health (issue 1574, ADR 0477)	2026-10-21 08:00:21 +00:00
jochen	d9336d11d0	pacman: the package manager's configuration, mirrors and cache as a module ... Mirrors were generated once and never again and caches never cleaned. The module holds node-package-manager (hq ADR 0207), declares pacman itself, owns /etc/pacman.conf whole — [options] cannot take an appended block — with the union of the enabled repositories and improved options, proven by pacman-conf in its test, and enables reflector.timer (its config owned) and paccache.timer. Fifteen tools from a Go bundle; transactions run as transient units so a call's timeout never kills pacman mid-transaction (to-be 42).	2026-10-04 12:50:20 +02:00