Uploaded image for project: 'Dev - Nexus Repo'
  1. Dev - Nexus Repo
  2. NEXUS-24899

Allow yum proxy to serve cached component removed from the remote

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: New
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 3.25.1
    • Fix Version/s: None
    • Component/s: Yum
    • Labels:
      None

      Description

      Remote yum repo only maintain one (latest) version of package at a time. Older/previous versions are removed as soon as new version is available.

      Assume I am using package abc with version 1.0 from EPEL. On client side, I am using yum to install it without any version specified. So, Nexus gets V 1.0 package from upstream and serves to client. All works well as version 1.0 is latest available in upstream. Now, If version 2.0 is available for same package abc in upstream. At this time, client will get v 2.0 with yum install, as 2.0 is now latest (this is my expectation). Note, at this time only v 2.0 is available in upstream and v 1.0 is removed.

      But now if I want to get v 1.0 the component would still exist in the proxy, but the metadata retrieved from the remote no longer has a reference to this version.

        Attachments

          Activity

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            cseney Cassandra Seney
            Last Updated By:
            Wes Wannemacher Wes Wannemacher
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Dates

              Created:
              Updated:
              Date of First Response:

                tigCommentSecurity.panel-title