Package as 1.1.1+keel2 so the build host gets the unit slots #6

Merged

marcos-mendez merged 1 commit from pkg/keel2 into master

2026-09-27 16:58:53 -03:00

marcos-mendez commented

2026-09-27 05:54:52 -03:00

(Migrated from github.com)

The two unit changes merged tonight, pull requests 4 and 5, live in share/product.mk. A build reads that file from the installed fab package, not from this checkout, and the build host installs 1.1.1+keel1: no UNITS selection, no unit removelist, no conf-vars. There, bt-layer's UNITS= override is ignored and every directory under unit.d is applied, which is exactly the re-run a child layer must not do.

This is a changelog entry and nothing else, so that the host can install the merged behaviour before the first component is extracted under decision 0010.

Test plan:

tests/coverage.sh (the package carries no code change)
built on the build host with bin/build-package --rebuild fab and installed, then the three-build equivalence comparison of decision 0010 for the mariadb component

The two unit changes merged tonight, pull requests 4 and 5, live in `share/product.mk`. A build reads that file from the installed `fab` package, not from this checkout, and the build host installs 1.1.1+keel1: no `UNITS` selection, no unit removelist, no `conf-vars`. There, `bt-layer`'s `UNITS=` override is ignored and every directory under `unit.d` is applied, which is exactly the re-run a child layer must not do. This is a changelog entry and nothing else, so that the host can install the merged behaviour before the first component is extracted under decision 0010. Test plan: - [x] `tests/coverage.sh` (the package carries no code change) - [ ] built on the build host with `bin/build-package --rebuild fab` and installed, then the three-build equivalence comparison of decision 0010 for the mariadb component