Block a user
mesh-tools
deleted branch fix/1773-clone-retries-a-lookup from novox/mesh-controller
2026-10-22 19:44:38 +00:00
f2a4363a1a
Merge pull request 'Clone from the forge again when the resolver does not answer, so a passing lookup failure does not fail a build (issue 1773)' (#440) from fix/1773-clone-retries-a-lookup into main
Clone from the forge again when the resolver does not answer, so a passing lookup failure does not fail a build (issue 1773)
Clone from the forge again when the resolver does not answer, so a passing lookup failure does not fail a build (issue 1773)
Merge check at fd4d26b4
Judged: head fd4d26b42cd7 merged into trunk 96441ea28a84; read beside it: mesh-catalog 2f05e70734cd, mesh-controller-main 96441ea28a84, mesh-host `4065b45ae84f…
mesh-tools
deleted branch fix/1841-keeper-state-dir from novox/mesh-catalog
2026-10-22 19:31:28 +00:00
ef1e98f867
Merge pull request 'Keep the pacman keeper's state in a directory of its own, not in the package database's /var/lib/pacman (issue 1841)' (#452) from fix/1841-keeper-state-dir into main
098c6d3ec7
Place pacman's state outside the package manager's own directory, and refuse a module directory in a system package's (issue 1841)
Keep the pacman keeper's state in a directory of its own, not in the package database's /var/lib/pacman (issue 1841)
Keep the pacman keeper's state in a directory of its own, not in the package database's /var/lib/pacman (issue 1841)
Merge check at 098c6d3e
Judged: head 098c6d3ec70f merged into trunk 2f05e70734cd; read beside it: mesh-controller 96441ea28a84, mesh-controller-main 96441ea28a84, mesh-host…
Clone from the forge again when the resolver does not answer, so a passing lookup failure does not fail a build (issue 1773)
Delivery novox/mesh-controller@fd4d26b42cd7 — proposed since 2026-10-22T19:27:45Z
Transitions
- 2026-10-22 19:27 (new) → proposed (announced):…
Clone from the forge again when the resolver does not answer, so a passing lookup failure does not fail a build (issue 1773)
Keep the pacman keeper's state in a directory of its own, not in the package database's /var/lib/pacman (issue 1841)
Delivery novox/mesh-catalog@098c6d3ec70f — proposed since 2026-10-22T19:26:00Z
Transitions
- 2026-10-22 19:26 (new) → proposed (announced): novox/mesh-c…
Keep the pacman keeper's state in a directory of its own, not in the package database's /var/lib/pacman (issue 1841)
cdfc63cf10
Merge pull request 'Let a process watch, put, list and delete its own state's keys, as a tools bundle can (upgrade safety, issue 1840, ADR 0507 §8)' (#69) from feat/upgrade-safety into main
f8b8f3a666
issue 1840/S2: take a narrowed watch's current values as a set, since the bus hands them in the order of their last revision
Let a process watch, put, list and delete its own state's keys, as a tools bundle can (upgrade safety, issue 1840, ADR 0507 §8)
96441ea28a
Merge pull request 'Keep each node's declared packages in a state the pacman module reads (upgrade safety, issue 1840, ADR 0507 §5)' (#439) from feat/upgrade-safety into main
abe356a262
Merge main and take the SDK at the milestone's mesh-sdk head 8892a117, which holds main's SDK and the milestone's (issue 1840)
3e3400f510
Take the SDK at the milestone's mesh-sdk head f8b8f3a6, which the delivery group's members must pin exactly (issue 1840)
e022a3fd6f
issue 1840/S3: look the declared packages up by name in the mirror's integration test, since every node also runs the mesh's own modules and their packages
Keep each node's declared packages in a state the pacman module reads (upgrade safety, issue 1840, ADR 0507 §5)
2f05e70734
Merge pull request 'Upgrade the nodes one at a time on the bus, with a package record, a kernel hold, an after-upgrade check, a rollback and a fallback kernel (upgrade safety, issues 1840 and 1841)' (#450) from feat/upgrade-safety into main
86ba54b06e
Take the SDK at the milestone's mesh-sdk head 8892a117 in pacman, which holds main's SDK and the milestone's (issue 1840)
0270027bf9
Take the SDK at the milestone's mesh-sdk head f8b8f3a6 in pacman, which the delivery group's members must pin exactly (issue 1840)
76a0a726f0
issue 1841/S15: put the booted kernel first when GRUB's menu is generated again, so the fallback kernel, sorted first by version, never becomes the default entry (ADR 0508 §9)