Майнтейнер: Andrew A. Vasilyev (Andrew A. Vasilyev)
Информация Пакеты Bugs and FR Repocop
Сообщения от repocop:пакет | статус | тест | сообщение |
---|---|---|---|
crtools-ovz-debuginfo-3.15.1.22-alt1.x86_64 |
![]() warn | rpm-filesystem-conflict-symlink-symlink | value of symlink /usr/lib/debug/usr/sbin/crtools.debug is different from the same symlink in the package crtools-debuginfo-3.15-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. |
crtools-ovz-debuginfo-3.15.1.22-alt1.x86_64 |
![]() warn | rpm-filesystem-conflict-symlink-file | symlink /usr/lib/debug/usr/sbin/criu.debug is a file in the package crtools-debuginfo-3.15-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. |
liblizardfs-client-devel-3.13.0-alt0.rc3.2.x86_64 |
![]() warn | library-pkgnames-static | package contains static library which has the same name as a shared library in the repository, but neither package name ends with -devel-static according to http://altlinux.org/Drafts/SharedLibs nor the package explicitly conflicts with the package with .so library |
libvcmmd-7.0.23-alt1.x86_64 |
![]() info | missing-url | Missing Url: in a package. |
libvcmmd-debuginfo-7.0.23-alt1.x86_64 |
![]() info | missing-url | Missing Url: in a package. |
libvcmmd-devel-7.0.23-alt1.x86_64 |
![]() info | missing-url | Missing Url: in a package. |
libvirt-client-7.0.0-alt2.x86_64 |
![]() fail | init-condrestart | /etc/rc.d/init.d/libvirt-guests: missing condrestart target. ERROR: alt-specific script %_sbindir/post_service (used in your %post_service macro) depends on condrestart. Please, fix./etc/rc.d/init.d/libvirt-guests: missing condstop target. ERROR: alt-specific script %_sbindir/preun_service (used in your %preun_service macro) depends on condstop. Please, fix. |
libvirt-daemon-7.0.0-alt2.x86_64 |
![]() experimental | systemd-check-socket-name | in libvirt-daemon-7.0.0-alt2.x86_64: there is a socket libvirtd-admin.socket but no service libvirtd-admin.service. Ask ildar@ why it is not right. in libvirt-daemon-7.0.0-alt2.x86_64: there is a socket libvirtd-ro.socket but no service libvirtd-ro.service. Ask ildar@ why it is not right. in libvirt-daemon-7.0.0-alt2.x86_64: there is a socket libvirtd-tcp.socket but no service libvirtd-tcp.service. Ask ildar@ why it is not right. in libvirt-daemon-7.0.0-alt2.x86_64: there is a socket libvirtd-tls.socket but no service libvirtd-tls.service. Ask ildar@ why it is not right. in libvirt-daemon-7.0.0-alt2.x86_64: there is a socket virtlockd-admin.socket but no service virtlockd-admin.service. Ask ildar@ why it is not right. in libvirt-daemon-7.0.0-alt2.x86_64: there is a socket virtlogd-admin.socket but no service virtlogd-admin.service. Ask ildar@ why it is not right. in libvirt-daemon-7.0.0-alt2.x86_64: there is a socket virtproxyd-admin.socket but no service virtproxyd-admin.service. Ask ... [the rest of the message is skipped] |
libvirt-daemon-7.0.0-alt2.x86_64 |
![]() experimental | checkbashisms | checkbashisms utility found possible bashisms in: /etc/rc.d/init.d/libvirtd |
libvirt-daemon-driver-interface-7.0.0-alt2.x86_64 |
![]() experimental | systemd-check-socket-name | in libvirt-daemon-driver-interface-7.0.0-alt2.x86_64: there is a socket virtinterfaced-admin.socket but no service virtinterfaced-admin.service. Ask ildar@ why it is not right. in libvirt-daemon-driver-interface-7.0.0-alt2.x86_64: there is a socket virtinterfaced-ro.socket but no service virtinterfaced-ro.service. Ask ildar@ why it is not right. |
libvirt-daemon-driver-lxc-7.0.0-alt2.x86_64 |
![]() experimental | systemd-check-socket-name | in libvirt-daemon-driver-lxc-7.0.0-alt2.x86_64: there is a socket virtlxcd-admin.socket but no service virtlxcd-admin.service. Ask ildar@ why it is not right. in libvirt-daemon-driver-lxc-7.0.0-alt2.x86_64: there is a socket virtlxcd-ro.socket but no service virtlxcd-ro.service. Ask ildar@ why it is not right. |
libvirt-daemon-driver-network-7.0.0-alt2.x86_64 |
![]() experimental | systemd-check-socket-name | in libvirt-daemon-driver-network-7.0.0-alt2.x86_64: there is a socket virtnetworkd-admin.socket but no service virtnetworkd-admin.service. Ask ildar@ why it is not right. in libvirt-daemon-driver-network-7.0.0-alt2.x86_64: there is a socket virtnetworkd-ro.socket but no service virtnetworkd-ro.service. Ask ildar@ why it is not right. |
libvirt-daemon-driver-nodedev-7.0.0-alt2.x86_64 |
![]() experimental | systemd-check-socket-name | in libvirt-daemon-driver-nodedev-7.0.0-alt2.x86_64: there is a socket virtnodedevd-admin.socket but no service virtnodedevd-admin.service. Ask ildar@ why it is not right. in libvirt-daemon-driver-nodedev-7.0.0-alt2.x86_64: there is a socket virtnodedevd-ro.socket but no service virtnodedevd-ro.service. Ask ildar@ why it is not right. |
libvirt-daemon-driver-nwfilter-7.0.0-alt2.x86_64 |
![]() experimental | systemd-check-socket-name | in libvirt-daemon-driver-nwfilter-7.0.0-alt2.x86_64: there is a socket virtnwfilterd-admin.socket but no service virtnwfilterd-admin.service. Ask ildar@ why it is not right. in libvirt-daemon-driver-nwfilter-7.0.0-alt2.x86_64: there is a socket virtnwfilterd-ro.socket but no service virtnwfilterd-ro.service. Ask ildar@ why it is not right. |
libvirt-daemon-driver-qemu-7.0.0-alt2.x86_64 |
![]() experimental | systemd-check-socket-name | in libvirt-daemon-driver-qemu-7.0.0-alt2.x86_64: there is a socket virtqemud-admin.socket but no service virtqemud-admin.service. Ask ildar@ why it is not right. in libvirt-daemon-driver-qemu-7.0.0-alt2.x86_64: there is a socket virtqemud-ro.socket but no service virtqemud-ro.service. Ask ildar@ why it is not right. |
libvirt-daemon-driver-secret-7.0.0-alt2.x86_64 |
![]() experimental | systemd-check-socket-name | in libvirt-daemon-driver-secret-7.0.0-alt2.x86_64: there is a socket virtsecretd-admin.socket but no service virtsecretd-admin.service. Ask ildar@ why it is not right. in libvirt-daemon-driver-secret-7.0.0-alt2.x86_64: there is a socket virtsecretd-ro.socket but no service virtsecretd-ro.service. Ask ildar@ why it is not right. |
libvirt-daemon-driver-storage-core-7.0.0-alt2.x86_64 |
![]() experimental | systemd-check-socket-name | in libvirt-daemon-driver-storage-core-7.0.0-alt2.x86_64: there is a socket virtstoraged-admin.socket but no service virtstoraged-admin.service. Ask ildar@ why it is not right. in libvirt-daemon-driver-storage-core-7.0.0-alt2.x86_64: there is a socket virtstoraged-ro.socket but no service virtstoraged-ro.service. Ask ildar@ why it is not right. |
libvirt-daemon-driver-vbox-7.0.0-alt2.x86_64 |
![]() experimental | systemd-check-socket-name | in libvirt-daemon-driver-vbox-7.0.0-alt2.x86_64: there is a socket virtvboxd-admin.socket but no service virtvboxd-admin.service. Ask ildar@ why it is not right. in libvirt-daemon-driver-vbox-7.0.0-alt2.x86_64: there is a socket virtvboxd-ro.socket but no service virtvboxd-ro.service. Ask ildar@ why it is not right. |
libvirt-libs-7.0.0-alt2.x86_64 |
![]() info | arch-dep-package-has-big-usr-share | 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. |
open-vm-tools-11.2.5-alt1.x86_64 |
![]() info | subdir-in-var-run | 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. |
open-vm-tools-11.2.5-alt1.x86_64 |
![]() info | big-changelog | Package contains big ChangeLog. Gzip it. |
open-vm-tools-11.2.5-alt1.x86_64 |
![]() experimental | checkbashisms | checkbashisms utility found possible bashisms in: /usr/bin/vm-support |
pve-qemu-common-5.1.0-alt4.x86_64 |
![]() warn | rpm-filesystem-conflict-file-file | File /usr/share/qemu/hppa-firmware.img conflicts with the package qemu-system-hppa-core-5.2.0-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. Files /usr/share/qemu/petalogix-ml605.dtb /usr/share/qemu/petalogix-s3adsp1800.dtb conflict with the package qemu-system-microblaze-core-5.2.0-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. |
pve-qemu-common-5.1.0-alt4.x86_64 |
![]() info | arch-dep-package-has-big-usr-share | 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. |
pve-qemu-system-5.1.0-alt4.x86_64 |
![]() warn | rpm-filesystem-conflict-file-file | File /usr/bin/qemu-system-aarch64 conflicts with the package qemu-system-aarch64-core-5.2.0-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. File /usr/bin/qemu-system-x86_64 conflicts with the package qemu-system-x86-core-5.2.0-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. There are file conflicts with the package qemu-tools-5.2.0-alt4.x86_64, for example, /usr/bin/elf2dmp (5 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. |
qemu-system-aarch64-core-5.2.0-alt4.x86_64 |
![]() warn | rpm-filesystem-conflict-file-file | File /usr/bin/qemu-system-aarch64 conflicts with the package pve-qemu-system-5.1.0-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. |
qemu-system-hppa-core-5.2.0-alt4.x86_64 |
![]() warn | rpm-filesystem-conflict-file-file | File /usr/share/qemu/hppa-firmware.img conflicts with the package pve-qemu-common-5.1.0-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. |
qemu-system-microblaze-core-5.2.0-alt4.x86_64 |
![]() warn | rpm-filesystem-conflict-file-file | Files /usr/share/qemu/petalogix-ml605.dtb /usr/share/qemu/petalogix-s3adsp1800.dtb conflict with the package pve-qemu-common-5.1.0-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. |
qemu-system-ppc-core-5.2.0-alt4.x86_64 |
![]() info | arch-dep-package-has-big-usr-share | 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. |
qemu-system-x86-core-5.2.0-alt4.x86_64 |
![]() warn | rpm-filesystem-conflict-file-file | File /usr/bin/qemu-system-x86_64 conflicts with the package pve-qemu-system-5.1.0-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. |
qemu-system-x86-core-5.2.0-alt4.x86_64 |
![]() warn | rpm-filesystem-conflict-symlink-file | symlink /usr/share/qemu/bios-microvm.bin is a file in the package pve-qemu-common-5.1.0-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. |
qemu-tools-5.2.0-alt4.x86_64 |
![]() warn | rpm-filesystem-conflict-file-file | There are file conflicts with the package pve-qemu-system-5.1.0-alt4.x86_64, for example, /usr/bin/elf2dmp (5 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. |
resource-agents-4.7.0-alt0.rc1.x86_64 |
![]() info | subdir-in-var-run | 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. |
resource-agents-4.7.0-alt0.rc1.x86_64 |
![]() experimental | checkbashisms | checkbashisms utility found possible bashisms in: /usr/sbin/rhev-check.sh |
thin-provisioning-tools-0.9.0-alt1.x86_64 |
![]() info | uncompressed-manpages | Package contains uncompressed manual pages. |
vcmmd-8.0.1-alt4.x86_64 |
![]() info | beehive-log-unpackaged-files-found-x86_64 | warning: Installed (but unpackaged) file(s) found: /usr/lib/tmpfiles.d/vcmmd-tmpfiles.conf |