1 Reply Latest reply on Aug 17, 2015 2:27 PM by Bill Robinson

    Red Hat Patching - How Do We Account For RPMs not in the catalog?

    Chad Johnson

      We have our Red Hat catalogs up and working fine for most systems.  However; on a few are non-red hat rpms.  Since these do not come from Red Hat they are not in the catalog. 

       

      This causes analysis to fail looking for pre-reqs for the installed rpm.

       

      Is there a way to perform analysis only against content which is in the catalog?

       

      BSA 8.3.01

        • 1. Re: Red Hat Patching - How Do We Account For RPMs not in the catalog?
          Bill Robinson

          Yum only looks at what rpms are in the catalog and what are on the box.  it has no way to check for a newer version of the custom rpm since it’s not in the catalog.  what is probably happening is the custom rpm is dependent on something being upgraded that is on the system and for which the catalog has a newer version. so if ‘redhat’ rpms are upgraded, won’t that require that your custom rpms be updated ?  eg, you have php-1.1 installed and customrpm-1.1.  upgrading php to 1.2 will require a customrpm-1.2…

           

          if you exclude the dependencies that the custom rpm has – eg php – that should work i think.