warn	TORCS-1.3.7-alt2.x86_64	value of symlink /usr/lib64/libtgfclient.so is different from the same symlink in the package speed-dreams-2.3.0-alt1.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.; ; 
warn	TORCS-debuginfo-1.3.7-alt2.x86_64	value of symlink /usr/lib/debug/usr/lib64/libtgfclient.so.debug is different from the same symlink in the package speed-dreams-debuginfo-2.3.0-alt1.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.; ; 
warn	clang-dpcpp-6.2.0-alt0.1.x86_64	value of symlink /usr/share/bash-completion/completions/clang-21 is different from the same symlink in the package clang21.1-21.1.5-alt0.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.; 
warn	clang-dpcpp-analyzer-6.2.0-alt0.1.x86_64	value of symlink /usr/share/man/man1/scan-build-21.1.xz is different from the same symlink in the package clang21.1-analyzer-21.1.5-alt0.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	clang21.1-21.1.5-alt0.1.x86_64	value of symlink /usr/share/bash-completion/completions/clang-21 is different from the same symlink in the package clang-dpcpp-6.2.0-alt0.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.; 
warn	clang21.1-analyzer-21.1.5-alt0.1.noarch	value of symlink /usr/share/man/man1/scan-build-21.1.xz is different from the same symlink in the package clang-dpcpp-analyzer-6.2.0-alt0.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.; 
warn	docs-alt-virtualization-one-11.0-alt0.1.noarch	value of symlink /usr/share/doc/documentation is different from the same symlink in the package docs-alt-virtualization-pve-11.0-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.; 
warn	docs-alt-virtualization-pve-11.0-alt2.noarch	value of symlink /usr/share/doc/documentation is different from the same symlink in the package docs-alt-virtualization-one-11.0-alt0.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	java-17-openjdk-headless-debuginfo-17.0.17.0.10-alt1.x86_64	value of symlink /usr/lib/debug/.build-id/c1/d494ca6d06ffe33aa59deabb5f3aaa66c64e2a.debug is different from the same symlink in the package java-21-openjdk-headless-debuginfo-21.0.9.0.10-alt1.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.; 
warn	java-21-openjdk-headless-debuginfo-21.0.9.0.10-alt1.x86_64	value of symlink /usr/lib/debug/.build-id/c1/d494ca6d06ffe33aa59deabb5f3aaa66c64e2a.debug is different from the same symlink in the package java-17-openjdk-headless-debuginfo-17.0.17.0.10-alt1.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.; 
warn	kde5-kimageannotator-devel-0.7.1-alt2.x86_64	value of symlink /usr/lib64/cmake/kImageAnnotator/kImageAnnotatorConfig.cmake is different from the same symlink in the package kde6-kimageannotator-devel-0.7.1-alt10.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.; atives.; .; 
warn	kde6-kimageannotator-devel-0.7.1-alt10.x86_64	value of symlink /usr/lib64/cmake/kImageAnnotator/kImageAnnotatorConfig.cmake is different from the same symlink in the package kde5-kimageannotator-devel-0.7.1-alt2.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.; atives.; .; 
warn	libLLVMSPIRVLib-devel-20.1.5-alt1.x86_64	value of symlink /usr/lib64/libLLVMSPIRVLib.so is different from the same symlink in the package libspirv-llvm15.0-translator-devel-15.0.15-alt2.g9c47ecad.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.; 
warn	libecpg6-13-debuginfo-13.22-alt2.x86_64	value of symlink /usr/lib/debug/usr/lib64/libpgtypes.so.3.debug is different from the same symlink in the package libecpg6-18-debuginfo-18.0-alt1.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.; s.; ; s.; 
warn	libecpg6-14-debuginfo-14.19-alt2.x86_64	value of symlink /usr/lib/debug/usr/lib64/libpgtypes.so.3.debug is different from the same symlink in the package libecpg6-18-debuginfo-18.0-alt1.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.; s.; ; s.; 
warn	libecpg6-15-debuginfo-15.14-alt2.x86_64	value of symlink /usr/lib/debug/usr/lib64/libpgtypes.so.3.debug is different from the same symlink in the package libecpg6-18-debuginfo-18.0-alt1.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.; s.; ; s.; 
warn	libecpg6-16-debuginfo-16.10-alt2.x86_64	value of symlink /usr/lib/debug/usr/lib64/libpgtypes.so.3.debug is different from the same symlink in the package libecpg6-18-debuginfo-18.0-alt1.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.; s.; ; s.; 
warn	libecpg6-17-1C-debuginfo-17.6-alt2.x86_64	value of symlink /usr/lib/debug/usr/lib64/libpgtypes.so.3.debug is different from the same symlink in the package libecpg6-18-debuginfo-18.0-alt1.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.; ; s.; ; 
warn	libecpg6-17-debuginfo-17.6-alt2.x86_64	value of symlink /usr/lib/debug/usr/lib64/libpgtypes.so.3.debug is different from the same symlink in the package libecpg6-18-debuginfo-18.0-alt1.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.; ; s.; ; 
warn	libecpg6-18-debuginfo-18.0-alt1.x86_64	value of symlink /usr/lib/debug/usr/lib64/libpgtypes.so.3.debug is different from the same symlink in the package libecpg6-17-debuginfo-17.6-alt2.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.; s.; ; s.; 
warn	libgcrypt-devel-1.10.2-alt2.x86_64	value of symlink /usr/lib64/libgcrypt.so is different from the same symlink in the package libgcrypt-gost-devel-1.8.5-alt6.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.; 
warn	libgcrypt-gost-devel-1.8.5-alt6.x86_64	value of symlink /usr/lib64/libgcrypt.so is different from the same symlink in the package libgcrypt-devel-1.10.2-alt2.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.; 
warn	libglfw-devel-2.7.9-alt1.x86_64	value of symlink /usr/lib64/libglfw.so is different from the same symlink in the package libglfw3-devel-3.4-alt2.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.; 
warn	libglfw3-devel-3.4-alt2.x86_64	value of symlink /usr/lib64/libglfw.so is different from the same symlink in the package libglfw-devel-2.7.9-alt1.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.; 
warn	libgs-devel-10.06.0-alt1.x86_64	value of symlink /usr/lib64/libgxps.so is different from the same symlink in the package libgxps-devel-0.3.2-alt1.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.; 
warn	libgxps-devel-0.3.2-alt1.x86_64	value of symlink /usr/lib64/libgxps.so is different from the same symlink in the package libgs-devel-10.06.0-alt1.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.; 
warn	libllama-devel-6869-alt1.x86_64	value of symlink /usr/lib64/libggml.so is different from the same symlink in the package libwhisper-cpp-devel-1.7.6-alt1.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.; ves.; 
warn	libmbedtls-3.6-devel-3.6.5-alt1.x86_64	value of symlink /usr/lib64/libmbedx509.so is different from the same symlink in the package libmbedtls-compat-devel-2.28.10-alt1.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.; .; 
warn	libmbedtls-compat-devel-2.28.10-alt1.x86_64	value of symlink /usr/lib64/libmbedx509.so is different from the same symlink in the package libmbedtls-3.6-devel-3.6.5-alt1.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.; .; 
warn	libpq5-13-devel-debuginfo-13.22-alt2.x86_64	value of symlink /usr/lib/debug/usr/lib64/libpq.so.debug is different from the same symlink in the package libpq5-17-devel-debuginfo-17.6-alt2.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.; s.; 
warn	libpq5-14-devel-debuginfo-14.19-alt2.x86_64	value of symlink /usr/lib/debug/usr/lib64/libpq.so.debug is different from the same symlink in the package libpq5-17-devel-debuginfo-17.6-alt2.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.; s.; 
warn	libpq5-15-devel-debuginfo-15.14-alt2.x86_64	value of symlink /usr/lib/debug/usr/lib64/libpq.so.debug is different from the same symlink in the package libpq5-17-devel-debuginfo-17.6-alt2.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.; s.; 
warn	libpq5-16-devel-debuginfo-16.10-alt2.x86_64	value of symlink /usr/lib/debug/usr/lib64/libpq.so.debug is different from the same symlink in the package libpq5-17-devel-debuginfo-17.6-alt2.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.; s.; 
warn	libpq5-17-1C-devel-debuginfo-17.6-alt2.x86_64	value of symlink /usr/lib/debug/usr/lib64/libpq.so.debug is different from the same symlink in the package libpq5-16-devel-debuginfo-16.10-alt2.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.; 
warn	libpq5-17-devel-debuginfo-17.6-alt2.x86_64	value of symlink /usr/lib/debug/usr/lib64/libpq.so.debug is different from the same symlink in the package libpq5-16-devel-debuginfo-16.10-alt2.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.; 
warn	libreadline-devel-8.2.10-alt1.x86_64	value of symlink /usr/lib64/libhistory.so is different from the same symlink in the package libreadline5-devel-5.2.14-alt7.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.; 
warn	libreadline5-devel-5.2.14-alt7.x86_64	value of symlink /usr/lib64/libhistory.so is different from the same symlink in the package libreadline-devel-8.2.10-alt1.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.; 
warn	libspirv-llvm15.0-translator-devel-15.0.15-alt2.g9c47ecad.x86_64	value of symlink /usr/lib64/libLLVMSPIRVLib.so is different from the same symlink in the package libLLVMSPIRVLib-devel-20.1.5-alt1.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.; 
warn	libucl-devel-1.03-alt4.x86_64	value of symlink /usr/lib64/libucl.so is different from the same symlink in the package libucl5-devel-0.8.1-alt1.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.; 
warn	libucl5-devel-0.8.1-alt1.x86_64	value of symlink /usr/lib64/libucl.so is different from the same symlink in the package libucl-devel-1.03-alt4.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.; 
warn	libwhisper-cpp-devel-1.7.6-alt1.x86_64	value of symlink /usr/lib64/libggml.so is different from the same symlink in the package libllama-devel-6869-alt1.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.; ves.; 
warn	mailutils-debuginfo-3.17.90-alt1.x86_64	value of symlink /usr/lib/debug/usr/bin/mailx.debug is different from the same symlink in the package mailx-debuginfo-8.1.2-alt9.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.; 
warn	mailx-debuginfo-8.1.2-alt9.x86_64	value of symlink /usr/lib/debug/usr/bin/mailx.debug is different from the same symlink in the package mailutils-debuginfo-3.17.90-alt1.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.; 
warn	ossp-uuid-1.6.2-alt2.x86_64	value of symlink /usr/bin/uuid is different from the same symlink in the package uuid-2.3.9-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	proxifier-1.0.3-alt2.noarch	value of symlink /usr/bin/pruby is different from the same symlink in the package proxifier2-1.1.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	proxifier2-1.1.0-alt1.noarch	value of symlink /usr/bin/pruby is different from the same symlink in the package proxifier-1.0.3-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.; 
warn	speed-dreams-2.3.0-alt1.x86_64	value of symlink /usr/lib64/libtgfclient.so is different from the same symlink in the package TORCS-1.3.7-alt2.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.; ; 
warn	speed-dreams-debuginfo-2.3.0-alt1.x86_64	value of symlink /usr/lib/debug/usr/lib64/libtgfclient.so.debug is different from the same symlink in the package TORCS-debuginfo-1.3.7-alt2.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.; ; 
warn	tomcat-el-3.0-api-9.0.109-alt1.noarch	value of symlink /usr/share/java/tomcat-el-api.jar is different from the same symlink in the package tomcat10-lib-10.1.20-alt3_jvm17.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	tomcat-jsp-2.3-api-9.0.109-alt1.noarch	value of symlink /usr/share/java/tomcat-jsp-api.jar is different from the same symlink in the package tomcat10-lib-10.1.20-alt3_jvm17.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	tomcat-servlet-4.0-api-9.0.109-alt1.noarch	value of symlink /usr/share/java/tomcat-servlet-api.jar is different from the same symlink in the package tomcat10-lib-10.1.20-alt3_jvm17.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	tomcat10-lib-10.1.20-alt3_jvm17.noarch	value of symlink /usr/share/java/tomcat-servlet-api.jar is different from the same symlink in the package tomcat-servlet-4.0-api-9.0.109-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	utils-0.34.0-alt1.noarch	value of symlink /usr/bin/edit is different from the same symlink in the package vi-traditional-4.1.3-alt1.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.; 
warn	uuid-2.3.9-alt1.noarch	value of symlink /usr/bin/uuid is different from the same symlink in the package ossp-uuid-1.6.2-alt2.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.; 
warn	vi-traditional-4.1.3-alt1.x86_64	value of symlink /usr/share/man/man1/view.1.xz is different from the same symlink in the package vim-common-9.1.1264-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
warn	vim-common-9.1.1264-alt1.noarch	value of symlink /usr/share/man/man1/view.1.xz is different from the same symlink in the package vi-traditional-4.1.3-alt1.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.;