This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revision | Last revisionBoth sides next revision | ||
linux:redhat:troubleshooting [2019/10/07 13:48] – lunetikk | linux:redhat:troubleshooting [2019/10/07 13:49] – lunetikk | ||
---|---|---|---|
Line 40: | Line 40: | ||
- | > | + | > |
- | + | If only after you have run the yum clean commands and rebuilt the database and you are still receiving the issue, then the only other option is to remove the package forcefully. But please note: If the package has many core dependencies and its removed, then this could break the server and it would be very difficult to recover from. Therefore this option is not recommended, | |
- | >If only after you have run the yum clean commands and rebuilt the database and you are still receiving the issue, then the only other option is to remove the package forcefully. But please note: If the package has many core dependencies and its removed, then this could break the server and it would be very difficult to recover from. Therefore this option is not recommended, | + | |
-Red Hat [[https:// | -Red Hat [[https:// | ||