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