Recommendations on handling of rpmnew and rpmsave files following Red Hat Enterpries Linux system update
Issue
- In which case (if not all) should one systematically analyse the changes brought by a new package when a
rpmsavefile is created? (based on the severity of theerrata? Based on the type of errata? Based on the type of package? etc...) - Can one simply ignore/delete rpmnew files?
- Other than by looking at the output of the
yum updatecommand, is there a command or method that would be best to identify packages that generated such files locally on the patched server? - What are the best practices commonly seen/used in large Enterprises for dealing with
rpmsaveandrpmnewfiles?
Environment
- Red Hat Enterprise Linux 4/5/6/7
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.
