Way to preserve upload-time metadata for pull-through repository

Offen

#1,371 erstellt am 07.9.2026 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit: 5/5
Geschätzter Aufwand: Über eine Woche
Anfängerfreundlichkeit: 45/100

Issue-Typ: Feature
Klarheit: Muss geklärt werden
Aktivitätsstatus: Aktiv
Tech-Stack: python
Bereich: api, backend

Rechercherichtung

Start by reviewing the simple repository API JSON responses mentioned in the issue and the related constraints in #1370. Define how a pull-through repository should preserve the source upload-time metadata, including whether this is configurable, and verify that copied packages expose the expected original timestamp.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

Feature Triage-Needed

Is your feature request related to a problem? Please describe.
I would like to use pulp's python plugin for a pull-through repository that mirrors pypi, so that I always have packages I depend on available locally (even if pypi goes down or a package is pulled from it, similar to left-pad). However, I also make use of dependency cooldowns using pip's --uploaded-prior-to and uv's --exclude-newer. A pulp pull-through repository shows the source upload-time metadata before it is copied, but after copying shows the time it was copied (uploaded to pulp). This prevents me from using pulp as a pull-through mirror alongside --uploaded-prior-to/--exclude-newer.

The upload-time changing when the package is copied seems like it could generally cause confusion or difficulty anyway.

Describe the solution you'd like
I don't have a clear idea of how this could be solved, but it makes sense to me for pull-through repositories to be transparent, and not change the upload-time metadata. Perhaps it could be an option when enabling pull-through?

Additional context
#1370 currently prevents actually using --uploaded-prior-to/--exclude-newer, but inspecting pulp's simple repository API JSON responses has made it apparent that this would be an issue for my use-case even if #1370 were fixed.

Vorherrschende Sprache: Python
Sterne: 49
Forks: 88
Ø Merge: 1 T. 10 Std.
Gemergte PRs (30 T.): 31

Beitragsleitfaden

Beitragsleitfaden öffnen

Erste Schritte

Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
Forken Sie das Repository und arbeiten Sie in einem Branch.
Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus pulp/pulp_python

RSS feed GUIDs are unstable when multi-architecture wheels arrive at different times Offen

Schwierigkeit 3/5 1-2 Tage Anfängerfreundlichkeit 68/100

pulp/pulp_python#1381 · Erstellt am 15.9.2026
Add standard "known vulnerabilities" metadata field, sourced from OSV Offen

Schwierigkeit 5/5 Über eine Woche Anfängerfreundlichkeit 45/100

pulp/pulp_python#1360 · Erstellt am 01.9.2026
Extension of Python REST API (repo index, metrics, content filters) Offen

Schwierigkeit 4/5 3-5 Tage Anfängerfreundlichkeit 52/100

pulp/pulp_python#1358 · Erstellt am 27.8.2026
Add support for SLSA attestation verification (pulp-service patch 0048) Offen

Feature

pulp/pulp_python#1340 · 1 zugewiesene Person · Erstellt am 20.8.2026
Pull-through cache: `.whl.metadata` (PEP 658) requests raise `ValueError: True is not in list` on 3.29.0 — residual case of #1083 Offen

Issue

Schwierigkeit 3/5 1-2 Tage Anfängerfreundlichkeit 58/100

pulp/pulp_python#1219 · 1 Kommentar · Erstellt am 30.4.2026

Alle Issues in pulp/pulp_python