Help finding obsolete RPMs in repos forming a propagation chain
oli99sc opened this issue · 5 comments
Provide a mechanism to easily identify RPMs that are not any longer needed in repos that for a propagation chain.
To explain propagation chain: Assume you have three repos: dev, staging, production.
With all systems in production connected to production, all systems in staging connected to production and staging, and all systems in dev connected to production, staging and dev.
In this case a artifact-1.0 in dev will never be installed, if in production there is a artifact-2.0 rpm.
As yum repo server should not know about these repo hierarchys, provide repo names as input.
http://yum.repo.hostname/maintenance/?targetRepo=production&sourceRepo=staging
With accept header application/json
will provide a detailed dataset for each rpm in source repo, obsoleted by a equal or higher version in target repo.
What about HTML output for human consumption?
On 14 November 2013 13:27, Oliver Schmitz notifications@github.com wrote:
http://yum.repo.hostname/maintenance/?targetRepo=production&sourceRepo=staging
With accept header application/json
will provide a detailed dataset for each rpm in source repo, obsoleted by
a equal or higher version in target repo.—
Reply to this email directly or view it on GitHubhttps://github.com//issues/31#issuecomment-28479928
.
Oops, I should consider the Architecture of the package when comparing, not only name and version.
Finally I will reduce the response size, not delivering all details of each rpm found.
This should to the job