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

Aperta
#1,371 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
45/100
Tipo di issue
Funzionalità
Chiarezza
Da chiarire
Stato di attività
Attiva
Stack tecnologico
python
Ambito
api, backend

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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.

Lingua principale
Python
Stelle
49
Fork
88
Merge medio
1g 10h
PR unite (30g)
31

Guida per i contributori

Apri la guida per i contributori

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di pulp/pulp_python

Tutte le issue di pulp/pulp_python

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.