fix: the project packages come from the Keel archive, not the build host staging #15
No reviewers
Labels
No labels
accessibility
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Keel-Linux/keel-postgresql!15
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "fix/keel-archive-not-staging"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Supersedes #13 (its commits are included). Same change as Keel-Linux/keel-mariadb#23.
trixie-stagingin the bootstrap, no 1001 pin in conf.d/main, nobin/keel-archive-check. That distribution holds inithooks keel5, confconsole keel2 and keel 0.3.5; pinned at 1001 the upgrade would have downgraded the layer.KEEL_APT_TRACK=testing(common#32). conf.d/main updates and upgrades them, thenbin/keel-project-packages(copied in byroot.patched/pre, removed by conf.d/main) requires each to be apt's candidate from the Keel archive in the track's suite. The version floors go.keel.sources, no 1001 pin.Tests:
tests/apt-files.bats,tests/project-packages.bats. Coverage: every measured file at 100 percent locally.appliance / boot-published-layercannot pass: no postgresql layer is published; the maintainer bypasses it.