RFE: Repositories should include all versions for a cycle until "refreshed"

[nazunalika]

Is this feature request related to a problem? If so, please describe it.

Current behavior of yumrepofs prioritizes latest versions of packages to be reposynced or used as it is presented. For users who need to fall back to an older version, this makes it difficult to roll back unless they have the old packages in cache or still have an older sync available, or do not use --delete on reposyncs.

For a given project, it should be possible to reposync all available packages and an option to remove all older versions (eg as a "refresh" or "preparing to build/release X.Y", or slimming down a continuous built project like lookahead).

Describe the solution you'd like to see

An option to turn off or on the ability to have older packages, optionally a "number" of older versions at max, perhaps.

Internal discussion lead to "max 3" being supported in a repository, similar to kernels installed to a system.

Have you considered alternative solutions/features? If so, please describe them.

N/A. Repo data cannot be arbitrarily signed outside the build system and createrepo takes too long to run on growing repositories (quantity and number of packages per repo).

Version and Build Information

Current. Cadence should be around 8.7/9.1 or 8.8/9.2.

Additional Context

Currently we are utilizing pungi and some scripts for Rocky Linux 8 to keep older packages around. A similar function would be neat for users of Rocky Linux 9 and beyond.

[mstg]

During the development cycle of yumrepofs, I changed the default behavior to always remove older artifacts. That should be enough to let empanadas handle that I assume

[NeilHanlon]

thinking out loud:

We could hardlink all assets to a vault/9.0 folder and then they'll be available on the vault mirror. this may help for 9.0 so we don't have to backport as many even if it's only for the next ~month.

[hdp7891000]

When will this problem be resolved?

[nazunalika]

This is a key feature we are wanting to introduce in v2. #120

…

On Wed, May 17, 2023, 19:11 epeng ***@***.***> wrote: When will this problem be resolved? — Reply to this email directly, view it on GitHub <#18 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACXQHKHAX65N3XQAHZCGOA3XGWAOHANCNFSM547LJHVA> . You are receiving this because you were assigned.Message ID: ***@***.***>

[hdp7891000]

This is a key feature we are wanting to introduce in v2. #120
…
On Wed, May 17, 2023, 19:11 epeng @.> wrote: When will this problem be resolved? — Reply to this email directly, view it on GitHub <#18 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACXQHKHAX65N3XQAHZCGOA3XGWAOHANCNFSM547LJHVA . You are receiving this because you were assigned.Message ID: @.>

Thank you, what is the estimated time? By that time, can the old packages of 9.0/9.1 be downloaded from https://dl.rockylinux.org/vault/?