Hi,
It is SLC, but how do I fix it?
# yum repolist help
Loaded plugins: changelog, kernel-module, protectbase, security,
tsflags, versionlock
EGI-trustanchors
| 1.9 kB 00:00
SGE_utils_patch
| 764 B 00:00
dag
| 1.1 kB 00:00
glite-CREAM
| 951 B 00:00
glite-CREAM_ext
| 951 B 00:00
glite-CREAM_updates
| 951 B 00:00
slc5-extras
| 2.1 kB 00:00
slc5-os
| 2.1 kB 00:00
slc5-updates
| 2.1 kB 00:00
Cheers,
Rod.
On 03/02/2011 11:51 AM, Steve Traylen wrote:
> On Wed, Mar 2, 2011 at 10:27 AM, Rodney Walker
> <[log in to unmask]> wrote:
>> Hi,
>> It is that time again - my next innocent yum update on the cream CE
>> results in
>>
> SLC? rather than SL?
>
> The tomcat5 package was a mistake in a recent release. The missing packages are
> in the SLC testing repo now to release probably Thursday I expect.
> This is an SLC
> and not SL only thing.
>
> The c-ares item used to be a conflict between gLite and EPEL
> but as of SLC5.6 c-ares is now in the OS so the gLite and the OS
> conflict. I think c-ares is also an SLC addition only but is at least
> in step with the EPEL package.
>
> glite-security-gss-2.0.0-6.sl5.x86_64 requiring libcares.so.0()(64bit)
> is supposedly fixed by: https://savannah.cern.ch/bugs/?57999
> which is closed.
>
> Steve.
>
>
>> # yum update
>> Loaded plugins: changelog, kernel-module, protectbase, security,
>> tsflags, versionlock
>> 354 packages excluded due to repository protections
>> Skipping security plugin, no data
>> Reading version lock configuration
>> Setting up Update Process
>> Resolving Dependencies
>> Skipping security plugin, no data
>> --> Running transaction check
>> --> Processing Dependency: libcares.so.0()(64bit) for package:
>> glite-security-gss
>> ---> Package c-ares.x86_64 0:1.6.0-5.el5 set to be updated
>> ---> Package tomcat5.x86_64 0:5.5.23-0jpp.16.el5 set to be updated
>> --> Processing Dependency: tomcat5-common-lib = 5.5.23-0jpp.16.el5 for
>> package: tomcat5
>> --> Processing Dependency: tomcat5-server-lib = 5.5.23-0jpp.16.el5 for
>> package: tomcat5
>> --> Processing Dependency: tomcat5-common-lib = 5.5.23-0jpp.16.el5 for
>> package: tomcat5
>> --> Processing Dependency: tomcat5-server-lib = 5.5.23-0jpp.16.el5 for
>> package: tomcat5
>> --> Finished Dependency Resolution
>> glite-security-gss-2.0.0-6.sl5.x86_64 from installed has depsolving problems
>> --> Missing Dependency: libcares.so.0()(64bit) is needed by package
>> glite-security-gss-2.0.0-6.sl5.x86_64 (installed)
>> tomcat5-5.5.23-0jpp.16.el5.x86_64 from slc5-updates has depsolving problems
>> --> Missing Dependency: tomcat5-common-lib = 5.5.23-0jpp.16.el5 is
>> needed by package tomcat5-5.5.23-0jpp.16.el5.x86_64 (slc5-updates)
>> tomcat5-5.5.23-0jpp.16.el5.x86_64 from slc5-updates has depsolving problems
>> --> Missing Dependency: tomcat5-server-lib = 5.5.23-0jpp.16.el5 is
>> needed by package tomcat5-5.5.23-0jpp.16.el5.x86_64 (slc5-updates)
>> Beginning Kernel Module Plugin
>> Finished Kernel Module Plugin
>> Error: Missing Dependency: libcares.so.0()(64bit) is needed by package
>> glite-security-gss-2.0.0-6.sl5.x86_64 (installed)
>> Error: Missing Dependency: tomcat5-server-lib = 5.5.23-0jpp.16.el5 is
>> needed by package tomcat5-5.5.23-0jpp.16.el5.x86_64 (slc5-updates)
>> Error: Missing Dependency: tomcat5-common-lib = 5.5.23-0jpp.16.el5 is
>> needed by package tomcat5-5.5.23-0jpp.16.el5.x86_64 (slc5-updates)
>> You could try using --skip-broken to work around the problem
>> You could try running: package-cleanup --problems
>> package-cleanup --dupes
>> rpm -Va --nofiles --nodigest
>>
>> I was told to exclude c-ares last time, but this does not help this time
>> around.
>>
>> Cheers,
>> Rod.
>>
>> --
>> Tel. +49 89 289 14152
>>
>
>
--
Tel. +49 89 289 14152
|