From f97b7dd544505960f83a965c07980834804c4b65 Mon Sep 17 00:00:00 2001 From: jochen Date: Sun, 27 Sep 2026 21:27:55 +0200 Subject: [PATCH] Undo: lavinmq cannot hold mesh-broker, and claiming it makes lavinmq unbuildable MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Putting the claim back was wrong on its own terms. `mesh-broker` delivers `mesh-bus`, and a seat that delivers a provision may only be held by a module that provides it — so the claim is refused at registration: lavinmq claims mesh-broker, whose holder answers for "mesh-bus", and lavinmq does not provide "mesh-bus" at mesh scope Which means the merged claim does not restore the holder, it stops lavinmq being built at all. Removed again. The seat being empty is still the live fault, and it has only one valid answer: the holder must provide `mesh-bus`, and the module that does is nats. Recorded against the rollout, because it moves a step that was optional into the critical path. --- modules/lavinmq/module.json | 6 ------ 1 file changed, 6 deletions(-) diff --git a/modules/lavinmq/module.json b/modules/lavinmq/module.json index f78368a..31f76e4 100644 --- a/modules/lavinmq/module.json +++ b/modules/lavinmq/module.json @@ -7,12 +7,6 @@ "scope": "mesh" } ], - "claims": [ - { - "name": "mesh-broker", - "scope": "mesh" - } - ], "capabilities": [ "container-runtime" ],