@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 /usr may not be marked as conffiles, since; /usr 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.57-alt1.noarch file-in-usr-marked-as-conffile warn Files below /usr may not be marked as conffiles, since; /usr 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.1.38-alt1.x86_64 rpm-filesystem-conflict-symlink-file warn symlink /usr/lib/debug/usr/bin/compare.debug is a file in the package zennode-debuginfo-1.2.1-alt1.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.;
rider collectd-5.12.0-alt6.x86_64 big-changelog info Package contains big ChangeLog. Gzip it.;
rider freeswitch-daemon-1.10.11-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.;
rider freeswitch-daemon-1.10.11-alt1.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.11-alt1.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.11-alt1.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.11-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.;
sem claws-mail-4.3.0-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-12-debuginfo-12.20-alt3.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-17-debuginfo-17.0-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.;
taf libecpg6-12-devel-static-12.20-alt3.x86_64 rpm-filesystem-conflict-file-file warn There are file conflicts with the package libecpg6-17-devel-static-17.0-alt2.x86_64, for example, /usr/lib64/libecpg.a (8 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 libecpg6-13-debuginfo-13.16-alt3.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-17-debuginfo-17.0-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.;
taf libecpg6-13-devel-static-13.16-alt3.x86_64 rpm-filesystem-conflict-file-file warn There are file conflicts with the package libecpg6-17-devel-static-17.0-alt2.x86_64, for example, /usr/lib64/libecpg.a (8 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 libecpg6-14-debuginfo-14.13-alt3.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-17-debuginfo-17.0-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.;
taf libecpg6-14-devel-static-14.13-alt3.x86_64 rpm-filesystem-conflict-file-file warn There are file conflicts with the package libecpg6-17-devel-static-17.0-alt2.x86_64, for example, /usr/lib64/libecpg.a (8 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 postgresql12-contrib-12.20-alt3.x86_64 rpm-filesystem-conflict-file-file warn There are file conflicts with the package postgresql17-contrib-17.0-alt2.x86_64, for example, /usr/bin/oid2name (72 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 postgresql12-llvmjit-12.20-alt3.x86_64 rpm-filesystem-conflict-file-file warn There are file conflicts with the package postgresql17-llvmjit-17.0-alt2.x86_64, for example, /usr/lib64/pgsql/bitcode/_int.index.bc (798 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 postgresql12-perl-12.20-alt3.x86_64 rpm-filesystem-conflict-file-file warn There are file conflicts with the package postgresql17-perl-17.0-alt2.x86_64, for example, /usr/lib64/pgsql/plperl.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.; ; licts are avoidable, consider using alternatives.;
taf postgresql12-python-12.20-alt3.x86_64 rpm-filesystem-conflict-file-file warn Files /usr/lib64/pgsql/plpython3.so /usr/share/pgsql/extension/plpython3u--1.0.sql conflict with the package postgresql17-python-17.0-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.; ;
taf postgresql12-server-12.20-alt3.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 postgresql12-server-12.20-alt3.x86_64 rpm-filesystem-conflict-file-file warn There are file conflicts with the package postgresql17-server-17.0-alt2.x86_64, for example, /etc/rc.d/init.d/postgresql (634 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 postgresql12-tcl-12.20-alt3.x86_64 rpm-filesystem-conflict-file-file warn There are file conflicts with the package postgresql17-tcl-17.0-alt2.x86_64, for example, /usr/lib64/pgsql/pltcl.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.; icts are avoidable, consider using alternatives.;
taf postgresql13-contrib-13.16-alt3.x86_64 rpm-filesystem-conflict-file-file warn There are file conflicts with the package postgresql17-contrib-17.0-alt2.x86_64, for example, /usr/bin/oid2name (42 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.16-alt3.x86_64 rpm-filesystem-conflict-file-file warn There are file conflicts with the package postgresql17-llvmjit-17.0-alt2.x86_64, for example, /usr/lib64/pgsql/bitcode/_int.index.bc (804 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.16-alt3.x86_64 rpm-filesystem-conflict-file-file warn File /usr/lib64/pgsql/plperl.so conflicts with the package postgresql17-perl-17.0-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.; ; ther. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.;
taf postgresql13-python-13.16-alt3.x86_64 rpm-filesystem-conflict-file-file warn Files /usr/lib64/pgsql/jsonb_plpython3.so /usr/lib64/pgsql/plpython3.so conflict with the package postgresql17-python-17.0-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.; ; ernatives.;
taf postgresql13-server-13.16-alt3.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.16-alt3.x86_64 rpm-filesystem-conflict-file-file warn There are file conflicts with the package postgresql17-server-17.0-alt2.x86_64, for example, /etc/rc.d/init.d/postgresql (35 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.16-alt3.x86_64 rpm-filesystem-conflict-file-file warn File /usr/lib64/pgsql/pltcl.so conflicts with the package postgresql17-tcl-17.0-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.; her. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.;
taf postgresql14-contrib-14.13-alt3.x86_64 rpm-filesystem-conflict-file-file warn There are file conflicts with the package postgresql17-contrib-17.0-alt2.x86_64, for example, /usr/bin/oid2name (39 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.13-alt3.x86_64 rpm-filesystem-conflict-file-file warn There are file conflicts with the package postgresql17-llvmjit-17.0-alt2.x86_64, for example, /usr/lib64/pgsql/bitcode/_int.index.bc (797 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.13-alt3.x86_64 rpm-filesystem-conflict-file-file warn File /usr/lib64/pgsql/plperl.so conflicts with the package postgresql17-perl-17.0-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.; ; nflicts are avoidable, consider using alternatives.;
taf postgresql14-python-14.13-alt3.x86_64 rpm-filesystem-conflict-file-file warn File /usr/lib64/pgsql/plpython3.so conflicts with the package postgresql17-python-17.0-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.; idable, consider using alternatives.; ernatives.;
taf postgresql14-server-14.13-alt3.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.13-alt3.x86_64 rpm-filesystem-conflict-file-file warn There are file conflicts with the package postgresql17-server-17.0-alt2.x86_64, for example, /etc/rc.d/init.d/postgresql (35 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.13-alt3.x86_64 rpm-filesystem-conflict-file-file warn File /usr/lib64/pgsql/pltcl.so conflicts with the package postgresql17-tcl-17.0-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.; her. 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.;