https://bugzilla.novell.com/show_bug.cgi?id=861081 https://bugzilla.novell.com/show_bug.cgi?id=861081#c3 --- Comment #3 from Richard Biener <rguenther@suse.com> 2014-02-12 10:16:44 UTC --- Yes, openblas-devel and blas-devel conflict as they both provide libblas.so. Applications are fine if the actual shared libraries do not conflict (well, if they would then a parallel install wouldn't work at all). I wonder if your users are allowed to change alternatives (which are system wide, so one user breaks the other?)? If they are allowed to change alternatives then they can be allowed to install/remove their desired *blas-devel package as well, no? That said, if you think that the alternatives mechanism is the way to go for providing libblas.so / liblapack.so (which might be so as those are quite "standard" names) then you have to coordinate this and get it done in the "right" way. The correct way is certainly not by alternativ-ing libblas.so.3 but by alternativ-ing libblas.so itself. Which of course needs alternative support from all packages that provide an alternative (not sure how you thought it could work without teaching the blas / lapack packages about the existence of alternatives of it) So, propose sth to opensuse-packaging/factory. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.