On Tue, Feb 22, 2005 at 01:10:06PM -0500, Ryan Williams wrote:
> >You (or someone) probably installed the package manually or something like
> >that, ie. not via up2date. Therefore the up2date profile in the server has
> >no knowledge of this package already installed in your machine, and try to
> >update it.
> >
> >Run 'up2date -p' to update your profile, then try again.
>
> The -p option doesn't fix the problem. It still gives the same error:
>
> Fetching Obsoletes list for channel: rhel-i386-es-3...
>
> Fetching rpm headers...
> ########################################
>
> Name Version Rel
> ----------------------------------------------------------
> xerces-j 2.2.1 11
> i386
>
>
> Testing package set / solving RPM inter-dependencies...
> ########################################
> RPM package conflict error. The message was:
> Test install failed because of package conflicts:
> package xerces-j-2.2.1-11 is already installed
>
>
> This is a new ES3 server install as of yesterday. We ran up2date
> yesterday without this issue and no RPMs have been manually installed.
> We do have Plesk on this box and did some psa related installs/upgrades
> which included the Tomcat server. I suppose Plesk could have installed
> it as part of that Java package.
Have a look at the output of:
rpm -qi xerces-j
And see if it's a Red Hat supplied package or different one. You can
also look at the timestamp of the install and see if it matches the
timeframe you did the Plesk install (whatever that is).
.../Ed
--
Ed Wilts, RHCE
Mounds View, MN, USA
mailto:ewilts@xxxxxxxxxx
Member #1, Red Hat Community Ambassador Program
--
redhat-list mailing list
unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/redhat-list
