Skip to content

The PowerShell suites still use the floating debian:bullseye-slim, not the pinned floor #43

Description

@Nemo-010

The shell suites pin the bullseye floor image to a dated tag, and the two PowerShell orchestrators still ask for the floating one, so the two suites build and test a different floor.

scripts/suite-lib.sh:192 defines CLD_FLOOR_IMAGE=debian:bullseye-20241111-slim and the comment above it calls that "THE ONE SPELLING of the bullseye floor image for both suites". scripts/run-evidence.sh:66 and scripts/run-appimage.sh:91 use it.

experiments/run.ps1:111 and experiments/appimage.ps1:211 still hardcode debian:bullseye-slim, and their headers at run.ps1:11 and appimage.ps1:10 describe the floating tag too.

The pin is not cosmetic. Per scripts/build.sh:34-44 and docs/building.md, the floating tag carries libc6 2.31-13+deb11u14 from the bullseye-security suite, while archive.debian.org (where the stage rewrites apt to) tops out at deb11u11; libc6-dev must version-match libc6 exactly, so the install fails with "held broken packages". That is the failure the dated tag was chosen to remove, and the PowerShell path still walks into it.

Fix: use debian:bullseye-20241111-slim in both PowerShell files and their headers, and note there that the tag must move with scripts/suite-lib.sh.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions