Repository navigation
Register source set 13 (perl 5.36.0-7+deb12u4) for v1.6.2 - #95
Merged
Merged
Conversation
The 1.6.2 hub publish would stop at "Locate Debian source bundle": a build simulation on a fresh debian:bookworm-slim (the Dockerfile release stage's apt-get install g++ libeigen3-dev python3), read on 2026-10-21 at 20:38 by the TX-SRCSET kit (box i-0f980a8da382d75e7, terminated), projects source set 074961f360ed4abee9baee6b2ea71aa45e3906a3b738bc3b6627ab60485f7362, which is not a registry row. Against the published 1.6.1-rc.1 image (set-02) two pairs moved: linux 6.1.187-1 -> 6.1.190-1 (already set-12's) and perl 5.36.0-7+deb12u3 -> 5.36.0-7+deb12u4 (bookworm-security). The base image digest and the Dockerfile are unchanged. Same failure mode as v1.6.1 (hub #72, set-12). set-13 is set-12 with that one pair replaced. Its holding release is v1.4.0, which already holds the other 83 sources (the very assets set-12's list names, unchanged lines; this change did not re-download them); perl_5.36.0-7_deb12u4.tar (sha256 03547f59095f502b449fe97061d1d34f7925d60cf679e4bc537d4ecd92c87ac5, 13670400 bytes) and set-13.SOURCES.list (sha256 8eec277f9c0f613003521bcf1d747423f2cc941a6ffac56c61748db0efe7176a, 10267 bytes) are to be attached to it BEFORE this row merges. How they were made: the recipe of the set-12 box run (lanes/core-srcset-161 A2), validated on the same box run by rebuilding set-02's adduser_3.134.tar byte for byte (sha256 d31971ab..., 276480 bytes); the perl .dsc (sha256 6f71e571...) was pinned on the Mac from security.debian.org and equals the copy served by deb.debian.org; every source file matched the .dsc Checksums-Sha256; the two orig tarballs are byte-identical (sha256 0f386dcc..., 10ac353b...) to the members of the already published perl_5.36.0-7_deb12u3.tar. The set-id of the new list, computed by sorting its unique source<TAB>version lines, is 074961f3... (and 362f8012... for set-12's list as a control). Registry row, README sentence, and the test's row count, tag tuple and uniqueness count updated. Not run: no local test run on this machine; the PR's CI is the proof. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The 1.6.2 hub publish would stop at "Locate Debian source bundle": a build
simulation on a fresh debian:bookworm-slim (the Dockerfile release stage's
apt-get install g++ libeigen3-dev python3), read on 2026-10-21 at 20:38 by the
TX-SRCSET kit (box i-0f980a8da382d75e7, terminated), projects source set
074961f360ed4abee9baee6b2ea71aa45e3906a3b738bc3b6627ab60485f7362, which is not a
registry row. Against the published 1.6.1-rc.1 image (set-02) two pairs moved:
linux 6.1.187-1 -> 6.1.190-1 (already set-12's) and perl 5.36.0-7+deb12u3 ->
5.36.0-7+deb12u4 (bookworm-security). The base image digest and the Dockerfile
are unchanged. Same failure mode as v1.6.1 (hub #72, set-12).
set-13 is set-12 with that one pair replaced. Its holding release is v1.4.0,
which already holds the other 83 sources (the very assets set-12's list names,
unchanged lines; this change did not re-download them);
perl_5.36.0-7_deb12u4.tar (sha256 03547f59095f502b449fe97061d1d34f7925d60cf679e4bc537d4ecd92c87ac5,
13670400 bytes) and set-13.SOURCES.list (sha256 8eec277f9c0f613003521bcf1d747423f2cc941a6ffac56c61748db0efe7176a,
10267 bytes) are to be attached to it BEFORE this row merges.
How they were made: the recipe of the set-12 box run (lanes/core-srcset-161 A2),
validated on the same box run by rebuilding set-02's adduser_3.134.tar byte for
byte (sha256 d31971ab..., 276480 bytes); the perl .dsc (sha256 6f71e571...) was
pinned on the Mac from security.debian.org and equals the copy served by
deb.debian.org; every source file matched the .dsc Checksums-Sha256; the two
orig tarballs are byte-identical (sha256 0f386dcc..., 10ac353b...) to the members
of the already published perl_5.36.0-7_deb12u3.tar. The set-id of the new list,
computed by sorting its unique sourceversion lines, is 074961f3... (and
362f8012... for set-12's list as a control).
Registry row, README sentence, and the test's row count, tag tuple and
uniqueness count updated. Not run: no local test run on this machine; the PR's
CI is the proof.
Co-Authored-By: Claude Sonnet 5.5 noreply@anthropic.com
Assets attached to v1.4.0 before this PR (read back): perl_5.36.0-7_deb12u4.tar sha256:03547f59…c87ac5 (13670400 B), set-13.SOURCES.list sha256:8eec277f…7176a (10267 B).
🤖 Generated with Claude Code