Pat Riehecky wrote:
The official SL6 link is at:
http://ftp.scientificlinux.org/linux/scientific/6x/external_products/
On C6 'yum install devtoolset-2' complains about no finding 'devtoolset-2-lucene'. The package is there and if I install it manually before calling yum, everything installs and works fine.
A metadata problem, perhaps?
-Chemal
On 08/29/2014 02:15 PM, Michael Lampe wrote:
Pat Riehecky wrote:
The official SL6 link is at:
http://ftp.scientificlinux.org/linux/scientific/6x/external_products/
On C6 'yum install devtoolset-2' complains about no finding 'devtoolset-2-lucene'. The package is there and if I install it manually before calling yum, everything installs and works fine.
A metadata problem, perhaps?
-Chemal
I've just rebuilt the metatdata up there. It should be better behaved now.
Pat
Pat Riehecky wrote:
On 08/29/2014 02:15 PM, Michael Lampe wrote:
Pat Riehecky wrote:
The official SL6 link is at:
http://ftp.scientificlinux.org/linux/scientific/6x/external_products/
On C6 'yum install devtoolset-2' complains about no finding 'devtoolset-2-lucene'. The package is there and if I install it manually before calling yum, everything installs and works fine.
A metadata problem, perhaps?
-Chemal
I've just rebuilt the metatdata up there. It should be better behaved now.
Pat
Unfortunately still not working ootb:
# yum install devtoolset-2 ... --> Finished Dependency Resolution Error: Package: devtoolset-2-eclipse-mylyn-3.9.1-4.el6.noarch (devtoolset) Requires: devtoolset-2-lucene Error: Package: 1:devtoolset-2-eclipse-platform-4.3.1-6.el6.x86_64 (devtoolset) Requires: devtoolset-2-lucene >= 2.9.4-8 Error: Package: devtoolset-2-lucene-contrib-3.6.0-16.el6.noarch (devtoolset) Requires: devtoolset-2-lucene = 3.6.0-16.el6 ...
-Michael
Michael Lampe wrote:
Pat Riehecky wrote:
On 08/29/2014 02:15 PM, Michael Lampe wrote:
Pat Riehecky wrote:
The official SL6 link is at:
http://ftp.scientificlinux.org/linux/scientific/6x/external_products/
On C6 'yum install devtoolset-2' complains about no finding 'devtoolset-2-lucene'. The package is there and if I install it manually before calling yum, everything installs and works fine.
A metadata problem, perhaps?
-Chemal
I've just rebuilt the metatdata up there. It should be better behaved now.
Pat
Unfortunately still not working ootb:
# yum install devtoolset-2 ... --> Finished Dependency Resolution Error: Package: devtoolset-2-eclipse-mylyn-3.9.1-4.el6.noarch (devtoolset) Requires: devtoolset-2-lucene Error: Package: 1:devtoolset-2-eclipse-platform-4.3.1-6.el6.x86_64 (devtoolset) Requires: devtoolset-2-lucene >= 2.9.4-8 Error: Package: devtoolset-2-lucene-contrib-3.6.0-16.el6.noarch (devtoolset) Requires: devtoolset-2-lucene = 3.6.0-16.el6 ...
-Michael
Interestingly, cern's version has the exact same problem with devtoolset-2-lucene.
They also have these packages in the x86_64 repo that you don't have:
devtoolset-2-valgrind-3.8.1-30.8.el6.i686 devtoolset-2-libitm-devel-4.8.2-15.1.el6.i686 devtoolset-2-systemtap-sdt-devel-2.1-8.el6.i686 devtoolset-2-oprofile-devel-0.9.8-6.el6.i686 devtoolset-2-libstdc++-devel-4.8.2-15.1.el6.i686 devtoolset-2-memstomp-0.1.4-11.el6.i686 devtoolset-2-junit-4.11-6.el6.1.noarch devtoolset-2-junit-demo-4.11-6.el6.1.noarch devtoolset-2-elfutils-devel-0.157-2.el6.i686 devtoolset-2-valgrind-devel-3.8.1-30.8.el6.i686 devtoolset-2-libatomic-devel-4.8.2-15.1.el6.i686 devtoolset-2-apache-commons-lang-2.6-12.el6.noarch devtoolset-2-libquadmath-devel-4.8.2-15.1.el6.i686 devtoolset-2-binutils-devel-2.23.52.0.1-10.el6.i686 devtoolset-2-libasan-devel-4.8.2-15.1.el6.i686 devtoolset-2-oprofile-jit-0.9.8-6.el6.i686 devtoolset-2-elfutils-libelf-devel-0.157-2.el6.i686
-Michael
On 09/02/2014 07:40 PM, Michael Lampe wrote:
Pat Riehecky wrote:
On 08/29/2014 02:15 PM, Michael Lampe wrote:
Pat Riehecky wrote:
The official SL6 link is at:
http://ftp.scientificlinux.org/linux/scientific/6x/external_products/
On C6 'yum install devtoolset-2' complains about no finding 'devtoolset-2-lucene'. The package is there and if I install it manually before calling yum, everything installs and works fine.
A metadata problem, perhaps?
-Chemal
I've just rebuilt the metatdata up there. It should be better behaved now.
Pat
Unfortunately still not working ootb:
# yum install devtoolset-2 ... --> Finished Dependency Resolution Error: Package: devtoolset-2-eclipse-mylyn-3.9.1-4.el6.noarch (devtoolset) Requires: devtoolset-2-lucene Error: Package: 1:devtoolset-2-eclipse-platform-4.3.1-6.el6.x86_64 (devtoolset) Requires: devtoolset-2-lucene >= 2.9.4-8 Error: Package: devtoolset-2-lucene-contrib-3.6.0-16.el6.noarch (devtoolset) Requires: devtoolset-2-lucene = 3.6.0-16.el6 ...
-Michael
Do you have any excludes set?
I show devtoolset-2-lucene within the primary.sqlite.bz2 and primary.xml.gz .
On VM I just spun up, yum install devtoolset-2 correctly locates devtoolset-2-lucene.
I've "remashed" the repo to include most of the 32bit packages you mentioned. Their inclusion on x86_64 seems a bit strange to me. I've no idea why I'd run 32 bit valgrind on a 64 bit system. But RH includes them so I've put them in.
Some packages were not included as they were released by CERN rather than RH.
You'll want to run a 'yum clean expire-cache' for the new metadata
Pat
Pat Riehecky wrote:
# yum install devtoolset-2 ... --> Finished Dependency Resolution Error: Package: devtoolset-2-eclipse-mylyn-3.9.1-4.el6.noarch (devtoolset) Requires: devtoolset-2-lucene Error: Package: 1:devtoolset-2-eclipse-platform-4.3.1-6.el6.x86_64 (devtoolset) Requires: devtoolset-2-lucene >= 2.9.4-8 Error: Package: devtoolset-2-lucene-contrib-3.6.0-16.el6.noarch (devtoolset) Requires: devtoolset-2-lucene = 3.6.0-16.el6 ...
-Michael
Do you have any excludes set?
Ah, stupid me. No excludes, of course, but it's similiar to the epel-repo discussion. 'devtoolset-2-lucene' obsoletes two system packages, namely 'lucene-devel' and 'lucene-demo', and priorities filters it out, because I have 'check_obsoletes=1'. (I've added this specifically for epel 6. They have new packages which obsolete system packages!)
So, sorry for the confusion, but I'm still wondering if it's a good idea for an SCL to obsolete system packages. It's against the whole idea of an SCL. But this probably should go to RH.
I've "remashed" the repo to include most of the 32bit packages you mentioned. Their inclusion on x86_64 seems a bit strange to me. I've no idea why I'd run 32 bit valgrind on a 64 bit system. But RH includes them so I've put them in.
The 32-bit devel packages let you compile 32-bit programs with 'gcc -m32 ...' and the 32-bit valgrind package adds some plugins for memory checking these too.
-Michael
-
Michael Lampe -
Pat Riehecky