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

Ouverte
#1,371 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Personne n'a encore pris cette issue.

Évaluation

Difficulté
5/5
Temps estimé
Plus d'une semaine
Accessibilité débutants
45/100
Type d'issue
Fonctionnalité
Clarté
À clarifier
Activité
Active
Stack technique
python
Domaine
api, backend

Piste de recherche

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.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

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.

Langage dominant
Python
Étoiles
49
Forks
88
Merge moyen
1 j 10 h
PR mergées (30 j)
31

Guide de contribution

Ouvrir le guide de contribution

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de pulp/pulp_python

Toutes les issues de pulp/pulp_python

Issues similaires

Plus d'issues Python

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.