Repository navigation
Make prebuilt replay replace the stale wheel in the local mirror #1432
Description
A successful prebuilt download can leave later builds using an older wheel. This silently builds with different contents from the artifact just downloaded.
To reproduce:
- Index an old wheel from
wheels-repo/downloads/. - Run
download-sequence --include-wheelsto fetch a configured prebuilt wheel with the same filename but different contents. - Refresh the mirror.
The fresh file is staged in wheels_prebuilt, but the mirror still serves the old file.
Expected: The mirror and subsequent builds use the freshly downloaded wheel. Add a regression test with identical filenames and different contents.
Observed on new-resolver-config at ff8d7683. Related: #1414 — review comment.
Metadata
Metadata
Assignees
Labels
No labels
Activity
LalatenduMohanty commentedon Nov 2, 2026
This doesn't block #1414:
mainhas the same behavior for legacypre_built: true:download-sequencesaves the fresh wheel towheels-repo/prebuilt, and the mirror links the older same-named copy inwheels-repo/downloadsfirst.source:packages, and onlydownload-sequence.build-sequencealready points the mirror at the fresh wheel (fix(resolver): honor configured prebuilt wheel resolvers #1393).wheels-repoavoids it.The underlying cause is broader: fromager treats a wheel filename as its identity. For example,
_is_wheel_built()reuses any same-named wheel on the local server. A proper fix should address that, not just this replay path.