viy	bsh-2.1.0-alt1_5jpp11.noarch	rpm-filesystem-conflict-file-file	warn	File /usr/bin/bsh conflicts with the package schilytools-2024.03.21-alt3.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.; 
viy	dogtag-ldapjdk-5.6.0-alt1.x86_64	arch-dep-package-consists-of-usr-share	info	The package consists of architecture-independent data in /usr/share, while it is an architecture-dependent package. This is wasteful of mirror space and bandwidth, as we then end up with multiple copies of this data, one for each architecture. If the data in /usr/share is not architecture-independent, it is a policy violation, and in this case, you should move that data elsewhere.; 
viy	java-common-1.7.0-alt1.noarch	freedesktop-desktop	info	desktop-file-validate utility printed the following message(s): /usr/share/applications/default-java.desktop: hint: value "X-ALTLinux-Java;" for key "Categories" in group "Desktop Entry" does not contain a registered main category; application might only show up in a "catch-all" section of the application menu; 
viy	java-common-1.7.0-alt1.noarch	missing-url	info	Missing Url: in a package.; 
viy	jflex-1.7.0-alt1_10jpp11.noarch	macos-resource-fork-file-in-package	warn	There is a file in the package with a name starting with <tt>._</tt>, the file name pattern used by Mac OS X to store resource forks in non-native file systems.  Such files are generally useless in packages and were usually accidentally included by copying complete directories from the source tarball.; 
viy	tomcat-el-3.0-api-9.0.109-alt1.noarch	altlinux-java-duplicate-jars	info	file /usr/share/java/tomcat-el-api.jar confilicts with package: tomcat10-lib-10.1.20-alt3_jvm17.noarch: if the jar do provide the same standard interface, it should be alternative. Otherwise it is recommended to rename the jar; 
viy	tomcat-el-3.0-api-9.0.109-alt1.noarch	rpm-filesystem-conflict-symlink-symlink	warn	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.; 
viy	tomcat-jsp-2.3-api-9.0.109-alt1.noarch	altlinux-java-duplicate-jars	info	file /usr/share/java/tomcat-jsp-api.jar confilicts with package: tomcat10-lib-10.1.20-alt3_jvm17.noarch: if the jar do provide the same standard interface, it should be alternative. Otherwise it is recommended to rename the jar; 
viy	tomcat-jsp-2.3-api-9.0.109-alt1.noarch	rpm-filesystem-conflict-symlink-symlink	warn	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.; 
viy	tomcat-servlet-4.0-api-9.0.109-alt1.noarch	altlinux-java-duplicate-jars	info	file /usr/share/java/tomcat-servlet-api.jar confilicts with package: tomcat10-lib-10.1.20-alt3_jvm17.noarch: if the jar do provide the same standard interface, it should be alternative. Otherwise it is recommended to rename the jar; 
viy	tomcat-servlet-4.0-api-9.0.109-alt1.noarch	rpm-filesystem-conflict-symlink-symlink	warn	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.; 
