andy	3proxy-0.6.1-alt3.x86_64	init-but-no-native-systemd	info	The package have SysV init script(s) but no native systemd files.; 
andy	3proxy-0.6.1-alt3.x86_64	init-lsb	fail	/etc/rc.d/init.d/3proxy: not systemd compatible: lsb init header missing and 3proxy.service is not present.  See http://www.altlinux.org/Services_Policy for details.; 
andy	3proxy-0.6.1-alt3.x86_64	rpm-filesystem-conflict-file-file	warn	File /usr/bin/proxy conflicts with the package python3-module-proxy-py-2.4.10-alt1.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.; using alternatives.; 
andy	3proxy-0.6.1-alt3.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.; 
andy	criu-4.2-alt1.x86_64	sisyphus_check	fail	sisyphus_check failed:  /ALT/Sisyphus/files/x86_64/RPMS/criu-4.2-alt1.x86_64.rpm: Invalid path names: /usr/lib/tmpfiles.d/criu.conf sisyphus_check: check-fhs ERROR: FHS violation; 
andy	drbd-reactor-1.10.0-alt1.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
andy	drbd-utils-9.33.0-alt1.x86_64	sisyphus_check	fail	sisyphus_check failed:  /ALT/Sisyphus/files/x86_64/RPMS/drbd-utils-9.33.0-alt1.x86_64.rpm: Invalid path names: /usr/lib/tmpfiles.d/drbd.conf sisyphus_check: check-fhs ERROR: FHS violation /ALT/Sisyphus/files/x86_64/RPMS/drbd-utils-9.33.0-alt1.x86_64.rpm: invalid udev rules path: /usr/lib/udev/rules.d/65-drbd.rules sisyphus_check: check-udev ERROR: udev rules path violation; 
andy	event-driven-servers-1.0-alt7.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.; 
andy	event-driven-servers-1.0-alt7.x86_64	unsafe-tmp-usage-in-scripts	fail	The test discovered scripts with errors which may be used by a user for damaging important system files. For example if a script uses in its work a temp file which is created in /tmp directory, then every user can create symlinks with the same name (pattern) in this directory in order to destroy or rewrite some system or another user's files. Scripts _must_ _use_ mktemp/tempfile or must use $TMPDIR. mktemp/tempfile is safest. $TMPDIR is safer than /tmp/ because libpam-tmpdir creates a subdirectory of /tmp that is only accessible by that user, and then sets TMPDIR and other variables to that. Hence, it doesn't matter nearly as much if you create a non-random filename, because nobody but you can access it. Found error in /etc/mavis/sample/tac_plus-ng.cfg: $ grep /tmp/ /etc/mavis/sample/tac_plus-ng.cfg id = tac_plus-ng { #debug = PACKET AUTHEN AUTHOR log mysyslog log accesslog { destination = /tmp/access.log } log authorlog { destination = /tmp/author.log } log authorlog2 { destination = ">/tmp/author2.log" } access log = mysyslog access log = accesslog authorization log = authorlog accounting log = mysyslog } } } # mavis module = tacinfo_cache { # directory = /tmp/tacinfo0 # } mavis module = groups { resolve gids = yes resolve gids attribute = TACMEMBER; 
andy	faces-xface-1.7.7-alt8.x86_64	freedesktop-categories	warn	Menu-related Additional Categories (http://standards.freedesktop.org/menu-spec/latest/apa.html) not found in /usr/share/applications/faces.desktop. Please add it or report a bug against this test if you already have registered one (not including menu unrelated ones as Core or Qt).; 
andy	faces-xface-1.7.7-alt8.x86_64	freedesktop-desktop	warn	desktop-file-validate utility exited abnormally with the following message(s): /usr/share/applications/faces.desktop: error: value "" for boolean key "Terminal" in group "Desktop Entry" contains invalid characters, boolean values must be "false" or "true"; /usr/share/applications/faces.desktop: error: value "Network;Mail;" for key "Categories" in group "Desktop Entry" contains an unregistered value "Mail"; values extending the format should start with "X-"; 
andy	faces-xface-1.7.7-alt8.x86_64	freedesktop-desktop-file-proposed-patch	warn	Please, apply the repocop patch for /usr/share/applications/faces.desktop.; 
andy	fence-agents-common-4.16.0-alt1.noarch	sisyphus_check	fail	sisyphus_check failed:  /ALT/Sisyphus/files/noarch/RPMS/fence-agents-common-4.16.0-alt1.noarch.rpm: Invalid path names: /usr/lib/tmpfiles.d/fence-agents.conf sisyphus_check: check-fhs ERROR: FHS violation; 
andy	festival-2.5-alt0.6.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
andy	ifupdown2-3.3.0.11-alt1.noarch	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
andy	kakasi-2.3.6-alt2.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; 
andy	ledmon-1.1.0-alt1.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
andy	ledmon-1.1.0-alt1.x86_64	uncompressed-manpages	info	Package contains uncompressed manual pages.; 
andy	lizardfs-client-3.13.0-alt0.rc4.1.1.x86_64	rpm-filesystem-conflict-symlink-file	warn	symlink /usr/share/man/man7/moosefs.7.xz is a file in the package moosefs-master-4.58.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.; 
andy	morse-2.6-alt1.x86_64	rpm-filesystem-conflict-symlink-file	warn	symlink /usr/bin/morse is a file in the package bsd-games-2.17-alt3_81.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.; 
andy	morse-debuginfo-2.6-alt1.x86_64	rpm-filesystem-conflict-symlink-file	warn	symlink /usr/lib/debug/usr/bin/morse.debug is a file in the package bsd-games-debuginfo-2.17-alt3_81.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.; 
andy	openbabel-3.1.1-alt4.5.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.; 
andy	phosphor-led-manager-1.0.0-alt0.2.gccca8eb3.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
andy	phosphor-led-sysfs-1.0.0-alt0.1.gf8548eeb.x86_64	sisyphus_check	fail	sisyphus_check failed:  /ALT/Sisyphus/files/x86_64/RPMS/phosphor-led-sysfs-1.0.0-alt0.1.gf8548eeb.x86_64.rpm: invalid udev rules path: /usr/lib/udev/rules.d/70-leds.rules sisyphus_check: check-udev ERROR: udev rules path violation; 
andy	phosphor-led-sysfs-1.0.0-alt0.1.gf8548eeb.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
andy	pi-hole-6.3-alt1.noarch	sisyphus_check	fail	sisyphus_check failed:  /ALT/Sisyphus/files/noarch/RPMS/pi-hole-6.3-alt1.noarch.rpm: Invalid path names: /usr/lib/tmpfiles.d/pi-hole.conf sisyphus_check: check-fhs ERROR: FHS violation; 
andy	pi-hole-6.3-alt1.noarch	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
andy	pi-hole-ftl-6.4.1-alt1.x86_64	sisyphus_check	fail	sisyphus_check failed:  /ALT/Sisyphus/files/x86_64/RPMS/pi-hole-ftl-6.4.1-alt1.x86_64.rpm: Invalid path names: /usr/lib/tmpfiles.d/pi-hole-ftl.conf sisyphus_check: check-fhs ERROR: FHS violation; 
andy	pi-hole-ftl-6.4.1-alt1.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
andy	pve-enable-0.1-alt2.x86_64	missing-url	info	Missing Url: in a package.; 
andy	python3-module-prometheus-pve-exporter-3.5.5-alt2.noarch	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
andy	ravada-2.4.2-alt1.noarch	pseudouser-added-as-real-user	fail	package added a pseudouser in its %pre/%post script as a real user. You should use -r option of useradd command to create a system account.; 
andy	ravada-2.4.2-alt1.noarch	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
andy	sbd-1.5.2-alt1.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
andy	swapd-1.0.5-alt2.x86_64	init-but-no-native-systemd	info	The package have SysV init script(s) but no native systemd files.; 
andy	syslinux1-1.62-alt4.2.qa1.x86_64	rpm-filesystem-conflict-file-file	warn	Files /usr/bin/lss16toppm /usr/bin/ppmtolss16 /usr/bin/syslinux conflict with the package syslinux-4.04-alt19.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.; 
andy	tac_plus-ng-1.0-alt7.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
andy	telnet-3.0-alt12.src	specfile-useradd-n	warn	 -n in useradd is compat option and can be removed any time. Use -N instead.; 
andy	udev-rules-hotplug-cpu-1.0-alt1.noarch	missing-url	info	Missing Url: in a package.; 
andy	volumes-profile-alt-server-v-1.1-alt1.noarch	rpm-filesystem-conflict-file-file	warn	File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-regular-0.5.2-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.; .; ives.; 
andy	volumes-profile-alt-server-v-1.1-alt1.noarch	unsafe-tmp-usage-in-scripts	fail	The test discovered scripts with errors which may be used by a user for damaging important system files. For example if a script uses in its work a temp file which is created in /tmp directory, then every user can create symlinks with the same name (pattern) in this directory in order to destroy or rewrite some system or another user's files. Scripts _must_ _use_ mktemp/tempfile or must use $TMPDIR. mktemp/tempfile is safest. $TMPDIR is safer than /tmp/ because libpam-tmpdir creates a subdirectory of /tmp that is only accessible by that user, and then sets TMPDIR and other variables to that. Hence, it doesn't matter nearly as much if you create a non-random filename, because nobody but you can access it. Found error in /usr/share/install2/initinstall.d/10-vm-profile.sh: $ grep /tmp/ /usr/share/install2/initinstall.d/10-vm-profile.sh #!/bin/sh # see also http://www.altlinux.org/Autoinstall message() { echo "vm-profile: $*" >>/tmp/vm-profile.log; } ROOT_MIN=7 # In Gb VAR_MIN=1 # In Gb mem="$(sed '/^MemTotal/s/[^0-9]//gp' /proc/meminfo)" # in kB; 
andy	wordtsar-0.3.719-alt1.x86_64	iconsdir	experimental	Please, move pixmaps from /usr/share/pixmaps to %_liconsdir, %_niconsdir, %_miconsdir according to their size. See http://www.altlinux.org/IconPathsPolicy.; 
bne	gitlab-runner-18.6.2-alt1.x86_64	sisyphus_check	fail	sisyphus_check failed:  /ALT/Sisyphus/files/x86_64/RPMS/gitlab-runner-18.6.2-alt1.x86_64.rpm: Invalid path names: /usr/lib/tmpfiles.d/gitlab-runner.conf sisyphus_check: check-fhs ERROR: FHS violation; 
cas	gambas-runtime-3.21.1-alt1.x86_64	iconsdir	experimental	Please, move pixmaps from /usr/share/pixmaps to %_liconsdir, %_niconsdir, %_miconsdir according to their size. See http://www.altlinux.org/IconPathsPolicy.; 
george	libxmlsec1-gcrypt-1.3.8-alt1.x86_64	altlinux-policy-shared-lib-contains-devel-so	info	SharedLibs Policy Draft violation: Shared Lib package should not contain symlink /usr/lib64/libxmlsec1-gcrypt.so but just /usr/lib64/libxmlsec1-gcrypt.so.1.3.8. According to SharedLibs Policy Draft, symlink /usr/lib64/libxmlsec1-gcrypt.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/libxmlsec1-gcrypt.so to \%files of libxmlsec1-gcrypt-1.3.8-alt1.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.; 
george	libxmlsec1-gnutls-1.3.8-alt1.x86_64	altlinux-policy-shared-lib-contains-devel-so	info	SharedLibs Policy Draft violation: Shared Lib package should not contain symlink /usr/lib64/libxmlsec1-gnutls.so but just /usr/lib64/libxmlsec1-gnutls.so.1.3.8. According to SharedLibs Policy Draft, symlink /usr/lib64/libxmlsec1-gnutls.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/libxmlsec1-gnutls.so to \%files of libxmlsec1-gnutls-1.3.8-alt1.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.; 
george	libxmlsec1-nss-1.3.8-alt1.x86_64	altlinux-policy-shared-lib-contains-devel-so	info	SharedLibs Policy Draft violation: Shared Lib package should not contain symlink /usr/lib64/libxmlsec1-nss.so but just /usr/lib64/libxmlsec1-nss.so.1.3.8. According to SharedLibs Policy Draft, symlink /usr/lib64/libxmlsec1-nss.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/libxmlsec1-nss.so to \%files of libxmlsec1-nss-1.3.8-alt1.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.; 
george	libxmlsec1-openssl-1.3.8-alt1.x86_64	altlinux-policy-shared-lib-contains-devel-so	info	SharedLibs Policy Draft violation: Shared Lib package should not contain symlink /usr/lib64/libxmlsec1-openssl.so but just /usr/lib64/libxmlsec1-openssl.so.1.3.8. According to SharedLibs Policy Draft, symlink /usr/lib64/libxmlsec1-openssl.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/libxmlsec1-openssl.so to \%files of libxmlsec1-openssl-1.3.8-alt1.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.; 
shaba	linstor-common-1.32.2-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.; 
shaba	linstor-controller-1.32.2-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	linstor-controller-1.32.2-alt1.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
shaba	linstor-satellite-1.32.2-alt1.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
shaba	moosefs-chunkserver-4.58.2-alt1.x86_64	sisyphus_check	fail	sisyphus_check failed:  /ALT/Sisyphus/files/x86_64/RPMS/moosefs-chunkserver-4.58.2-alt1.x86_64.rpm: invalid udev rules path: /usr/lib/udev/rules.d/80-moosefs-chunkserver.rules sisyphus_check: check-udev ERROR: udev rules path violation; 
shaba	open-vm-tools-13.0.5-alt1.x86_64	big-changelog	info	Package contains big ChangeLog. Gzip it.; 
shaba	open-vm-tools-13.0.5-alt1.x86_64	sisyphus_check	fail	sisyphus_check failed:  /ALT/Sisyphus/files/x86_64/RPMS/open-vm-tools-13.0.5-alt1.x86_64.rpm: Invalid path names: /usr/lib/tmpfiles.d/open-vm-tools-vgauthd.conf sisyphus_check: check-fhs ERROR: FHS violation /ALT/Sisyphus/files/x86_64/RPMS/open-vm-tools-13.0.5-alt1.x86_64.rpm: invalid udev rules path: /usr/lib/udev/rules.d/90-vmware-guest-tools.rules /usr/lib/udev/rules.d/98-open-vm-tools.rules /usr/lib/udev/rules.d/99-vmware-scsi-udev.rules sisyphus_check: check-udev ERROR: udev rules path violation; 
shaba	open-vm-tools-13.0.5-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.; 
shaba	open-vm-tools-desktop-13.0.5-alt1.x86_64	sisyphus_check	fail	sisyphus_check failed:  /ALT/Sisyphus/files/x86_64/RPMS/open-vm-tools-desktop-13.0.5-alt1.x86_64.rpm: Invalid path names: /usr/lib/tmpfiles.d/open-vm-tools-desktop.conf sisyphus_check: check-fhs ERROR: FHS violation; 
shaba	proxmox-widget-toolkit-5.0.4-alt2.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.; 
shaba	pve-backup-restore-image-0.5-alt1.x86_64	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.; ; 
shaba	pve-backup-restore-image-0.5-alt1.x86_64	missing-url	info	Missing Url: in a package.; 
shaba	pve-backup-restore-image-0.5-alt1.x86_64	rpm-package-is-obsoleted	warn	The package is  obsoleted by the package proxmox-backup-restore-image-4.0.14.1-alt1.x86_64, but is still alive and in the repository. Consider removing the package, or, if you want the package to be alive, ask the maintainer of proxmox-backup-restore-image-4.0.14.1-alt1.x86_64 to remove Obsoletes: tag.; 
shaba	pve-container-6.0.9-alt1.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
shaba	pve-firewall-6.0.3-alt1.x86_64	sisyphus_check	fail	sisyphus_check failed:  /ALT/Sisyphus/files/x86_64/RPMS/pve-firewall-6.0.3-alt1.x86_64.rpm: Invalid path names: /usr/lib/tmpfiles.d/pve-firewall.conf sisyphus_check: check-fhs ERROR: FHS violation; 
shaba	pve-firewall-6.0.3-alt1.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
shaba	pve-ha-manager-5.0.4-alt1.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
shaba	pve-qemu-server-9.0.18-alt1.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
shaba	resource-agents-4.17.0-alt1.x86_64	sisyphus_check	fail	sisyphus_check failed:  /ALT/Sisyphus/files/x86_64/RPMS/resource-agents-4.17.0-alt1.x86_64.rpm: Invalid path names: /usr/lib/tmpfiles.d/resource-agents.conf sisyphus_check: check-fhs ERROR: FHS violation; 
shaba	resource-agents-4.17.0-alt1.x86_64	unsafe-tmp-usage-in-scripts	fail	The test discovered scripts with errors which may be used by a user for damaging important system files. For example if a script uses in its work a temp file which is created in /tmp directory, then every user can create symlinks with the same name (pattern) in this directory in order to destroy or rewrite some system or another user's files. Scripts _must_ _use_ mktemp/tempfile or must use $TMPDIR. mktemp/tempfile is safest. $TMPDIR is safer than /tmp/ because libpam-tmpdir creates a subdirectory of /tmp that is only accessible by that user, and then sets TMPDIR and other variables to that. Hence, it doesn't matter nearly as much if you create a non-random filename, because nobody but you can access it. Found error in /usr/lib/ocf/resource.d/heartbeat/rabbitmq-server-ha: $ grep /tmp/ /usr/lib/ocf/resource.d/heartbeat/rabbitmq-server-ha </parameter> <parameter name="debug" unique="0" required="0"> <longdesc lang="en"> The debug flag for agent (${OCF_RESKEY_binary}) instance. In the /tmp/ directory will be created rmq-* files for log some operations and ENV values inside OCF-script. </longdesc> <shortdesc lang="en">AMQP server (${OCF_RESKEY_binary}) debug flag</shortdesc> <content type="boolean" default="${OCF_RESKEY_debug_default}" /> </parameter> local rc=$OCF_ERR_GENERIC local LH="${LL} monitor:" ocf_log debug "${LH} action start." if ocf_is_true "${OCF_RESKEY_debug}"; then d=`date '+%Y%m%d %H:%M:%S'` echo $d >> /tmp/rmq-monitor.log env >> /tmp/rmq-monitor.log echo "$d [monitor] start='${OCF_RESKEY_CRM_meta_notify_start_uname}' stop='${OCF_RESKEY_CRM_meta_notify_stop_uname}' active='${OCF_RESKEY_CRM_meta_notify_active_uname}' inactive='${OCF_RESKEY_CRM_meta_notify_inactive_uname}'" >> /tmp/rmq-ocf.log fi get_monitor rc=$? ocf_log debug "${LH} role: ${OCF_RESKEY_CRM_meta_role}" ocf_log debug "${LH} result: $rc" -- local LH="${LL} start:" local nowtime if ocf_is_true "${OCF_RESKEY_debug}"; then d=`date '+%Y%m%d %H:%M:%S'` echo $d >> /tmp/rmq-start.log env >> /tmp/rmq-start.log echo "$d [start] start='${OCF_RESKEY_CRM_meta_notify_start_uname}' stop='${OCF_RESKEY_CRM_meta_notify_stop_uname}' active='${OCF_RESKEY_CRM_meta_notify_active_uname}' inactive='${OCF_RESKEY_CRM_meta_notify_inactive_uname}'" >> /tmp/rmq-ocf.log fi ocf_log info "${LH} action begin." get_status -- local rc=$OCF_ERR_GENERIC local LH="${LL} stop:" if ocf_is_true "${OCF_RESKEY_debug}"; then d=$(date '+%Y%m%d %H:%M:%S') echo $d >> /tmp/rmq-stop.log env >> /tmp/rmq-stop.log echo "$d [stop] start='${OCF_RESKEY_CRM_meta_notify_start_uname}' stop='${OCF_RESKEY_CRM_meta_notify_stop_uname}' active='${OCF_RESKEY_CRM_meta_notify_active_uname}' inactive='${OCF_RESKEY_CRM_meta_notify_inactive_uname}'" >> /tmp/rmq-ocf.log fi ocf_log info "${LH} action begin." ocf_log info "${LH} Deleting master attribute" -- local LH="${LL} notify:" local nodelist if ocf_is_true "${OCF_RESKEY_debug}"; then d=`date '+%Y%m%d %H:%M:%S'` echo $d >> /tmp/rmq-notify.log env >> /tmp/rmq-notify.log echo "$d [notify] ${OCF_RESKEY_CRM_meta_notify_type}-${OCF_RESKEY_CRM_meta_notify_operation} promote='${OCF_RESKEY_CRM_meta_notify_promote_uname}' demote='${OCF_RESKEY_CRM_meta_notify_demote_uname}' master='${OCF_RESKEY_CRM_meta_notify_master_uname}' slave='${OCF_RESKEY_CRM_meta_notify_slave_uname}' start='${OCF_RESKEY_CRM_meta_notify_start_uname}' stop='${OCF_RESKEY_CRM_meta_notify_stop_uname}' active='${OCF_RESKEY_CRM_meta_notify_active_uname}' inactive='${OCF_RESKEY_CRM_meta_notify_inactive_uname}'" >> /tmp/rmq-ocf.log fi if [ "${OCF_RESKEY_CRM_meta_notify_type}" = 'post' ] ; then # POST- anything notify section case "$OCF_RESKEY_CRM_meta_notify_operation" in -- local rc=$OCF_ERR_GENERIC local LH="${LL} promote:" if ocf_is_true "${OCF_RESKEY_debug}"; then d=$(date '+%Y%m%d %H:%M:%S') echo $d >> /tmp/rmq-promote.log env >> /tmp/rmq-promote.log echo "$d [promote] start='${OCF_RESKEY_CRM_meta_notify_start_uname}' stop='${OCF_RESKEY_CRM_meta_notify_stop_uname}' active='${OCF_RESKEY_CRM_meta_notify_active_uname}' inactive='${OCF_RESKEY_CRM_meta_notify_inactive_uname}'" >> /tmp/rmq-ocf.log fi ocf_log info "${LH} action begin." get_monitor; 
vt	coccinelle-1.3.1-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	Files /usr/bin/spatch /usr/share/man/man1/spatch.1.xz conflict 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.; 
