libtrilinos10-devel-11.12.1-alt2.x86_64	altlinux-python-obsolete-buildreq-python-dev	warn	python-dev is obsolete according to Python Policy (http://www.altlinux.org/Python_Policy). Please, use BuildRequires: python-devel.; 
libtrilinos10-devel-11.12.1-alt2.x86_64	rpm-filesystem-conflict-symlink-symlink	warn	value of symlink /usr/lib64/libgtest.so is different from the same symlink in the package libgtest-devel-1.8.0-alt4.M80P.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
libtrios10-devel-11.12.1-alt2.x86_64	rpm-filesystem-conflict-symlink-symlink	warn	value of symlink /usr/lib64/libtrios_nnti.so is different from the same symlink in the package libnnti-devel-2.0-alt1.git20150304.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib64/libtrios_support.so is different from the same symlink in the package libnnti-devel-2.0-alt1.git20150304.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
trilinos10-headers-11.12.1-alt2.x86_64	rpm-filesystem-conflict-file-file	warn	File /usr/include/gtest/gtest.h conflicts with the package libgtest-devel-1.8.0-alt4.M80P.1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; File /usr/include/gmres.h conflicts with the package libimlxx-devel-1.2a-alt2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; There are file conflicts with the package libnnti-devel-2.0-alt1.git20150304.x86_64, for example, /usr/include/Trios_config.h (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.;