Oops, forgot to paste the link. It looks like you got the answer, but
to complete my response here you go:
https://access.redhat.com/solutions/10185
Quoting pdou...@xmission.com:
I have had to deal with this problem, usually due to updates that are
unsupported by 3rd party apps. You can exc
I have had to deal with this problem, usually due to updates that are
unsupported by 3rd party apps. You can exclude individual packages
from your updates. I think this article should help.
Quoting "Rose, John B" :
It seems as though “yum” update has replaced Apache modules
installed in
Thanks John
On 11/10/17, 4:38 PM, "John Iliffe" wrote:
yum doesn't know when you install a programme by compiling it that it is
there unless you update the package history database, so it goes by it's
previous record (the apache version that you superseded).
There is a yu
yum doesn't know when you install a programme by compiling it that it is
there unless you update the package history database, so it goes by it's
previous record (the apache version that you superseded).
There is a yum option to exclude specific packages from a yum update. I
seem to recall tha
It seems as though “yum” update has replaced Apache modules installed in the
default installation, that we had removed after the initial install because
they weren’t used.
Is there some way to prevent that from happening?
thanks
