Skip to content

compat.sycl-runtime: the entry is frozen, the behaviour is not - #357

Merged
Sunrisepeak merged 1 commit into
mainfrom
fix/sycl-runtime-frozen-claim
Sep 5, 2026
Merged

compat.sycl-runtime: the entry is frozen, the behaviour is not#357
Sunrisepeak merged 1 commit into
mainfrom
fix/sycl-runtime-frozen-claim

Conversation

@Sunrisepeak

Copy link
Copy Markdown
Member

The 2026.09.07 commit said 2026.09.06 "installs the farm it always did". That
is false and the sandbox verification showed it: there is one install() in
this file and it never reads pkginfo.version(), so a version key selects the
anchor URL and nothing else. A store holding both versions shows the same
libcuda.so.1 under each.

The behaviour is intended -- the content is generated rather than downloaded --
but "kept and frozen" reads as a promise about what an old pin installs, and it
is not one.

The 2026.09.07 commit said 2026.09.06 "installs the farm it always did". That
is false and the sandbox verification showed it: there is one `install()` in
this file and it never reads `pkginfo.version()`, so a version key selects the
anchor URL and nothing else. A store holding both versions shows the same
`libcuda.so.1` under each.

The behaviour is intended -- the content is generated rather than downloaded --
but "kept and frozen" reads as a promise about what an old pin installs, and it
is not one.
@Sunrisepeak
Sunrisepeak merged commit 9ffe886 into main Sep 5, 2026
11 checks passed
@Sunrisepeak
Sunrisepeak deleted the fix/sycl-runtime-frozen-claim branch September 5, 2026 23:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants