Hi, I’m trying to upgrade a grid system wich contains EMI/UMD software… and things are getting wrong. I’m getting : Error: Package: glite-wms-brokerinfo-access-3.5.0-3.sl6.x86_64 (@irfu-emi3-base) Requires: libclassad_ns.so.1()(64bit) Removing: classads-1.0.10-1.el6.x86_64 (@epel) libclassad_ns.so.1()(64bit) Obsoleted By: condor-classads-8.4.0-1.el6.x86_64 (htcondor-stable)
Not found Error: Package: glite-lb-common-9.1.1-1.el6.x86_64 (@epel) Requires: libclassad.so.1()(64bit) Removing: classads-1.0.10-1.el6.x86_64 (@epel) libclassad.so.1()(64bit) Obsoleted By: condor-classads-8.4.0-1.el6.x86_64 (htcondor-stable) Not found Available: condor-7.6.4-1.x86_64 (htcondor-stable) libclassad.so.1()(64bit) Available: condor-7.6.5-1.x86_64 (htcondor-stable) libclassad.so.1()(64bit) Available: condor-7.6.6-1.x86_64 (htcondor-stable) libclassad.so.1()(64bit) Available: condor-7.6.7-1.x86_64 (htcondor-stable) libclassad.so.1()(64bit) Available: condor-7.6.8-1.x86_64 (htcondor-stable) libclassad.so.1()(64bit) Available: condor-7.6.9-1.x86_64 (htcondor-stable) libclassad.so.1()(64bit) Available: condor-7.6.10-1.x86_64 (htcondor-stable) libclassad.so.1()(64bit) Removing: condor-8.2.8-313322.x86_64 (@htcondor-stable) Not found Updated By: condor-8.4.0-1.el6.x86_64 (htcondor-stable) Not found Available: condor-7.8.0-37683.x86_64 (htcondor-stable) Not found Available: condor-7.8.1-43996.i386 (htcondor-stable)
Not found (…) My question therefore is : how should things be upgraded ? Should condor be kept in a 8.2 version on the startd only ? From what I understand, the new condor packages obsolete previous functionalities without being backward compatible with dependent software… I checked and the condor-classads RPM effectively obsoletes : classads <= 1.0.10 classads-static <= 1.0.10 But nothing provides “libclassad_ns.so.1()(64bit)or libclassad.so.1” Why prevent the other non-conflicting RPMs in epel from being installed if that’s breaking things ? Any idea how I should update the system, but more important : how can I make sure that further node reinstallations won’t break because the new condors are not compatible with what’s published in epel ? I could off course blacklist condor 8.4 in yum, but I’d like to avoid messing with temporary (?) things which will break with next releases… and I don’t see why 8.4 could not be installed in parallel of the old “classads”
rpm ? Thanks |