@cpan	perl-DBD-XBase-1.08-alt2.noarch	rpm-filesystem-conflict-file-file	warn	File /usr/bin/dbfdump conflicts with the package libshape-1.5.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.; 
@cpan	perl-HTML-Template-JIT-0.05-alt2.2.noarch	missing-url	info	Missing Url: in a package.; 
@cpan	perl-XML-SAX-1.02-alt1.noarch	file-in-usr-marked-as-conffile	warn	Files below <tt>/usr</tt> may not be marked as conffiles, since;  <tt>/usr</tt> might be mounted read-only and thus, the local system;  administrator would not have a chance to modify this configuration;  file.; ; 
aris	gnumeric-data-1.12.59-alt1.noarch	file-in-usr-marked-as-conffile	warn	Files below <tt>/usr</tt> may not be marked as conffiles, since;  <tt>/usr</tt> might be mounted read-only and thus, the local system;  administrator would not have a chance to modify this configuration;  file.; ; 
ender	perl-MIDI-0.84-alt1.noarch	missing-url	info	Missing Url: in a package.; 
rider	ImageMagick-tools-debuginfo-7.1.2.8-alt1.x86_64	rpm-filesystem-conflict-symlink-file	warn	symlink /usr/lib/debug/usr/bin/compare.debug is a file in the package schilytools-debuginfo-2024.03.21-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.; 
rider	collectd-5.12.0-alt7.x86_64	big-changelog	info	Package contains big ChangeLog. Gzip it.; 
rider	freeswitch-daemon-1.10.12-alt4.x86_64	arch-dep-package-has-big-usr-share	info	The package has a significant amount 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.; 
rider	freeswitch-daemon-1.10.12-alt4.x86_64	init-but-no-native-systemd	info	The package have SysV init script(s) but no native systemd files.; 
rider	freeswitch-daemon-1.10.12-alt4.x86_64	init-lsb	fail	/etc/rc.d/init.d/freeswitch: not systemd compatible: lsb init header missing and freeswitch.service is not present.  See http://www.altlinux.org/Services_Policy for details.; 
rider	freeswitch-daemon-1.10.12-alt4.x86_64	sisyphus_check	fail	sisyphus_check failed:  /ALT/Sisyphus/files/x86_64/RPMS/freeswitch-daemon-1.10.12-alt4.x86_64.rpm: Invalid path names: /usr/lib/tmpfiles.d/freeswitch.conf sisyphus_check: check-fhs ERROR: FHS violation; 
rider	freeswitch-daemon-1.10.12-alt4.x86_64	subdir-in-var-run	info	Found a subdir in /var/run or /var/lock. /var/run and /var/lock may be mounted as temporary filesystems, so the init.d scripts must handle this correctly. This will typically amount to creating any required subdirectories dynamically when the init.d script is run, rather than including them in the package and relying on rpm to create them.; 
rider	freeswitch-webui-1.10.12-alt4.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.; 
sem	claws-mail-4.3.1-alt1.x86_64	arch-dep-package-has-big-usr-share	info	The package has a significant amount 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.; 
shaba	hivex-1.3.24-alt1.x86_64	library-pkgnames	info	package contains public library which is used in external packages: name should be lib* according to http://altlinux.org/Drafts/SharedLibs; 
taf	libecpg6-13-debuginfo-13.22-alt2.x86_64	rpm-filesystem-conflict-symlink-symlink	warn	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.; 
taf	libecpg6-14-debuginfo-14.19-alt2.x86_64	rpm-filesystem-conflict-symlink-symlink	warn	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.; 
taf	libpq5-13-devel-13.22-alt2.x86_64	altlinux-policy-shared-lib-contains-devel-so	info	SharedLibs Policy Draft violation: Shared Lib package should not contain symlink /usr/lib64/libpq.so but just /usr/lib64/libpq.so.5.13. According to SharedLibs Policy Draft, symlink /usr/lib64/libpq.so should be placed in a special subpackage named lib<name>-devel. If you have already packaged this symlink in lib<name>-devel, just append \%exclude /usr/lib64/libpq.so to \%files of libpq5-13-devel-13.22-alt2.x86_64. Otherwise, move the symlink into the subpackage lib<name>-devel. There is a known exception for case the .so file is not a shared lib but a plugin that is never directly linked with. Please report such a case to repocop test.; 
taf	libpq5-13-devel-debuginfo-13.22-alt2.x86_64	rpm-filesystem-conflict-symlink-symlink	warn	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.; 
taf	libpq5-13-devel-static-13.22-alt2.x86_64	rpm-filesystem-conflict-file-file	warn	File /usr/lib64/libpq.a conflicts with the package libpq5-18-devel-static-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.; 
taf	libpq5-14-devel-14.19-alt2.x86_64	altlinux-policy-shared-lib-contains-devel-so	info	SharedLibs Policy Draft violation: Shared Lib package should not contain symlink /usr/lib64/libpq.so but just /usr/lib64/libpq.so.5.14. According to SharedLibs Policy Draft, symlink /usr/lib64/libpq.so should be placed in a special subpackage named lib<name>-devel. If you have already packaged this symlink in lib<name>-devel, just append \%exclude /usr/lib64/libpq.so to \%files of libpq5-14-devel-14.19-alt2.x86_64. Otherwise, move the symlink into the subpackage lib<name>-devel. There is a known exception for case the .so file is not a shared lib but a plugin that is never directly linked with. Please report such a case to repocop test.; 
taf	libpq5-14-devel-debuginfo-14.19-alt2.x86_64	rpm-filesystem-conflict-symlink-symlink	warn	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.; 
taf	libpq5-14-devel-static-14.19-alt2.x86_64	rpm-filesystem-conflict-file-file	warn	File /usr/lib64/libpq.a conflicts with the package libpq5-18-devel-static-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.; 
taf	postgresql13-contrib-13.22-alt2.x86_64	rpm-filesystem-conflict-file-file	warn	There are file conflicts with the package postgresql18-contrib-18.0-alt1.x86_64, for example, /usr/bin/oid2name (49 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.; ; 
taf	postgresql13-llvmjit-13.22-alt2.x86_64	rpm-filesystem-conflict-file-file	warn	There are file conflicts with the package postgresql18-llvmjit-18.0-alt1.x86_64, for example, /usr/lib64/pgsql/bitcode/_int.index.bc (820 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.; s.; .; 
taf	postgresql13-perl-13.22-alt2.x86_64	rpm-filesystem-conflict-file-file	warn	File /usr/lib64/pgsql/plperl.so conflicts with the package postgresql18-perl-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.; ; 
taf	postgresql13-python-13.22-alt2.x86_64	rpm-filesystem-conflict-file-file	warn	There are file conflicts with the package postgresql18-python-18.0-alt1.x86_64, for example, /usr/lib64/pgsql/jsonb_plpython3.so (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.; 
taf	postgresql13-server-13.22-alt2.x86_64	arch-dep-package-has-big-usr-share	info	The package has a significant amount 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.; 
taf	postgresql13-server-13.22-alt2.x86_64	rpm-filesystem-conflict-file-file	warn	There are file conflicts with the package postgresql18-server-18.0-alt1.x86_64, for example, /etc/rc.d/init.d/postgresql (36 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.; ; 
taf	postgresql13-tcl-13.22-alt2.x86_64	rpm-filesystem-conflict-file-file	warn	File /usr/lib64/pgsql/pltcl.so conflicts with the package postgresql18-tcl-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.; ; 
taf	postgresql14-contrib-14.19-alt2.x86_64	rpm-filesystem-conflict-file-file	warn	There are file conflicts with the package postgresql18-contrib-18.0-alt1.x86_64, for example, /usr/bin/oid2name (47 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.; ; 
taf	postgresql14-llvmjit-14.19-alt2.x86_64	rpm-filesystem-conflict-file-file	warn	There are file conflicts with the package postgresql18-llvmjit-18.0-alt1.x86_64, for example, /usr/lib64/pgsql/bitcode/_int.index.bc (801 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.; s.; .; 
taf	postgresql14-perl-14.19-alt2.x86_64	rpm-filesystem-conflict-file-file	warn	File /usr/lib64/pgsql/plperl.so conflicts with the package postgresql18-perl-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.; ; 
taf	postgresql14-python-14.19-alt2.x86_64	rpm-filesystem-conflict-file-file	warn	There are file conflicts with the package postgresql18-python-18.0-alt1.x86_64, for example, /usr/lib64/pgsql/jsonb_plpython3.so (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.; 
taf	postgresql14-server-14.19-alt2.x86_64	arch-dep-package-has-big-usr-share	info	The package has a significant amount 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.; 
taf	postgresql14-server-14.19-alt2.x86_64	rpm-filesystem-conflict-file-file	warn	There are file conflicts with the package postgresql18-server-18.0-alt1.x86_64, for example, /etc/rc.d/init.d/postgresql (37 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.; ; 
taf	postgresql14-tcl-14.19-alt2.x86_64	rpm-filesystem-conflict-file-file	warn	File /usr/lib64/pgsql/pltcl.so conflicts with the package postgresql18-tcl-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.; ; 
viy	libmapsdb-devel-0.17-alt2.x86_64	missing-url	info	Missing Url: in a package.; 
viy	perl-Data-Array2ArrayMap-Hash-XSTree-0.15-alt1.x86_64	missing-url	info	Missing Url: in a package.; 
viy	perl-Data-Array2ArrayMap-Hash-XSTree-debuginfo-0.15-alt1.x86_64	missing-url	info	Missing Url: in a package.; 
viy	perl-Data-Array2ArrayMap-SDB-0.17-alt2.x86_64	missing-url	info	Missing Url: in a package.; 
viy	perl-Data-Array2ArrayMap-SDB-debuginfo-0.17-alt2.x86_64	missing-url	info	Missing Url: in a package.; 
viy	perl-Sys-CPUtime-0.10-alt4.2.x86_64	missing-url	info	Missing Url: in a package.; 
viy	perl-Sys-CPUtime-debuginfo-0.10-alt4.2.x86_64	missing-url	info	Missing Url: in a package.; 
