jschoubben d70135bf08 issue 1841/S5: join the upgrade parts to the keeper's loop, so a node's log, records, unfinished runs and asks are taken up by its own keeper ...

At its start the keeper reads the log into runs once, prunes old records and carries unfinished runs on;
after every released lock it carries them on again; it takes each ask at <node>.* and prunes records daily.
The root helper's client is a constructor (newRootActs) the helper replaces; until then every act is
refused, named.

2026-10-22 14:39:59 +02:00

..

testdata

issue 1840/S9: prove pacman's output puts no command line or environment on the bus

2026-10-22 14:37:00 +02:00

acts.go

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

aftercheck_test.go

issue 1841/S6: check after every upgrade the files it left, the news since the last one, units newly failed and a restart needed, so the operator sees what an upgrade asks of them

2026-10-22 14:37:58 +02:00

aftercheck.go

issue 1841/S6: check after every upgrade the files it left, the news since the last one, units newly failed and a restart needed, so the operator sees what an upgrade asks of them

2026-10-22 14:37:58 +02:00

bus_fake_test.go

Keep every upgrade as a run on the bus and read the log's past upgrades once, so pacman_upgrades answers every node's history without asking a machine (issue 1841/S2)

2026-10-22 14:29:23 +02:00

busshapes_test.go

issue 1841/S6: check after every upgrade the files it left, the news since the last one, units newly failed and a restart needed, so the operator sees what an upgrade asks of them

2026-10-22 14:37:58 +02:00

dkms_test.go

Hold a kernel an installed DKMS module's own bound excludes, with its headers, so an upgrade never leaves a machine whose storage driver cannot load (issue 1841/S4)

2026-10-22 14:31:53 +02:00

dkms.go

issue 1841/S4: format the gate's patterns as gofmt does, which the merge check requires

2026-10-22 14:32:01 +02:00

history.go

pacman: the package manager's configuration, mirrors and cache as a module

2026-10-04 12:50:20 +02:00

installed_health_test.go

issue 1840/S6: keep the node's packages in installed, read at the keeper's start and at every released lock

2026-10-22 14:31:33 +02:00

installed_health.go

issue 1840/S6: keep the node's packages in installed, read at the keeper's start and at every released lock

2026-10-22 14:31:33 +02:00

keeper_bus_test.go

issue 1840/S9: prove pacman's output puts no command line or environment on the bus

2026-10-22 14:37:00 +02:00

keeper_hooks_test.go

issue 1841/S5: join the upgrade parts to the keeper's loop, so a node's log, records, unfinished runs and asks are taken up by its own keeper

2026-10-22 14:39:59 +02:00

keeper_integration_test.go

issue 1841/S5: join the upgrade parts to the keeper's loop, so a node's log, records, unfinished runs and asks are taken up by its own keeper

2026-10-22 14:39:59 +02:00

keeper_manifest_test.go

Declare the pacman keeper and its bus shapes, so upgrades run as rounds on the bus instead of a weekly timer on every node at once (issue 1841/S1, with 1840/S5's manifest)

2026-10-22 14:23:22 +02:00

keeper_test.go

issue 1840/S6: emit through the same EventSink as the upgrade parts, so one connection serves both

2026-10-22 14:32:10 +02:00

keeper.go

issue 1841/S5: join the upgrade parts to the keeper's loop, so a node's log, records, unfinished runs and asks are taken up by its own keeper

2026-10-22 14:39:59 +02:00

machine_test.go

pacman: the package manager's configuration, mirrors and cache as a module

2026-10-04 12:50:20 +02:00

machine.go

issue 1840/S6: keep the node's packages in installed, read at the keeper's start and at every released lock

2026-10-22 14:31:33 +02:00

main.go

Merge branch 'feat/upgrade-safety' into p2

2026-10-22 14:36:14 +02:00

manifest_test.go

Declare the pacman keeper and its bus shapes, so upgrades run as rounds on the bus instead of a weekly timer on every node at once (issue 1841/S1, with 1840/S5's manifest)

2026-10-22 14:23:22 +02:00

mirrors.go

pacman: the package manager's configuration, mirrors and cache as a module

2026-10-04 12:50:20 +02:00

news.go

pacman: the package manager's configuration, mirrors and cache as a module

2026-10-04 12:50:20 +02:00

packages.go

issue 1840/S6: keep the node's packages in installed, read at the keeper's start and at every released lock

2026-10-22 14:31:33 +02:00

pacman_test.go

Merge branch 'feat/upgrade-safety' into p2

2026-10-22 14:36:14 +02:00

query.go

issue 1840/S8: answer the package view from the bus, so every node is read at once and none is asked

2026-10-22 14:36:11 +02:00

record_test.go

Take the node's package record before a run and read it back, refusing a run whose packages are not current, so a rollback always has a true record to return to (issue 1841/S3)

2026-10-22 14:30:34 +02:00

record.go

Take the node's package record before a run and read it back, refusing a run whose packages are not current, so a rollback always has a true record to return to (issue 1841/S3)

2026-10-22 14:30:34 +02:00

runs_test.go

Keep every upgrade as a run on the bus and read the log's past upgrades once, so pacman_upgrades answers every node's history without asking a machine (issue 1841/S2)

2026-10-22 14:29:23 +02:00

shape_test.go

pacman: the package manager's configuration, mirrors and cache as a module

2026-10-04 12:50:20 +02:00

shapes.go

issue 1841/S6: check after every upgrade the files it left, the news since the last one, units newly failed and a restart needed, so the operator sees what an upgrade asks of them

2026-10-22 14:37:58 +02:00

templates_test.go

Feature 57 (config and provisioning): release the catalogue, the reviewed release branch merged with main, on top of main

2026-10-16 09:42:45 +00:00

transaction_test.go

issue 1841/S6: check after every upgrade the files it left, the news since the last one, units newly failed and a restart needed, so the operator sees what an upgrade asks of them

2026-10-22 14:37:58 +02:00

transaction.go

issue 1841/S6: check after every upgrade the files it left, the news since the last one, units newly failed and a restart needed, so the operator sees what an upgrade asks of them

2026-10-22 14:37:58 +02:00

updates_test.go

issue 1840/S7: prove updates is read at start, after a transaction, after the mirrors and daily, and written only on change

2026-10-22 14:33:20 +02:00

upgrade_health.go

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

upgrades.go

issue 1841/S6: check after every upgrade the files it left, the news since the last one, units newly failed and a restart needed, so the operator sees what an upgrade asks of them

2026-10-22 14:37:58 +02:00

view_test.go

issue 1840/S8: answer the package view from the bus, so every node is read at once and none is asked

2026-10-22 14:36:11 +02:00

view.go

issue 1840/S8: answer the package view from the bus, so every node is read at once and none is asked

2026-10-22 14:36:11 +02:00

watch.go

issue 1840/S6: keep the node's packages in installed, read at the keeper's start and at every released lock

2026-10-22 14:31:33 +02:00