rirusha	apm-0.6.3-alt1.x86_64	sisyphus_check	fail	sisyphus_check failed:  /ALT/Sisyphus/files/x86_64/RPMS/apm-0.6.3-alt1.x86_64.rpm: Invalid path names: /usr/lib/tmpfiles.d/apm.conf sisyphus_check: check-fhs ERROR: FHS violation; 
rirusha	bootc-1.16.8-alt1.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
rirusha	bootupd-0.2.32-alt3.x86_64	systemd-but-no-native-init	experimental	The package have native systemd file(s) but no  SysV init scripts.
udalov	apmdo-0.5.2-alt1.x86_64	unsafe-tmp-usage-in-scripts	info	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/doc/apmdo-0.5.2/examples/example/src/show-params.sh: $ grep /tmp/ /usr/share/doc/apmdo-0.5.2/examples/example/src/show-params.sh echo "action dir: $(pwd)" echo "EDITION=${EDITION:-}" echo "ENABLE_GPU=${ENABLE_GPU:-}" echo "HOSTNAME_=${HOSTNAME_:-}" date > /tmp/apmdo-example.applied echo "marker written: /tmp/apmdo-example.applied"; 
