amatch-0.4.0-alt1.noarch rpm-filesystem-conflict-symlink-file warn symlink /usr/bin/agrep is a file in the package agrep-tre-0.8.0-alt2.2.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.; apache2-mod-passenger-6.0.11-alt2.x86_64 altlinux-policy-obsolete-httpd2-reload info This package contains httpd2 restart/reload calls in its post/un scripts. But those calls are deprecated by httpd2.filetrigger that activates by files in /etc/httpd2/ or %_libdir/apache2/modules/. It should be safe to remove those calls and rely on the filetrigger instead.; canorus-0.7.3.git45e82ec-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.; coinor-osi-doc-0.108.8-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.; compass-1.1.0-alt1.noarch rpm-filesystem-conflict-symlink-file warn symlink /usr/bin/compass is a file in the package gnome-compass-0.4.0-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.; curlftpfs-0.9.2.1-alt0.1.x86_64 rpm-package-is-obsoleted warn The package is obsoleted by the package fuse-curlftpfs-0.9.2-alt3.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 fuse-curlftpfs-0.9.2-alt3.x86_64 to remove Obsoletes: tag.; curlftpfs-ng-0.9.3.1-alt0.1.x86_64 rpm-filesystem-conflict-file-file warn Files /usr/bin/curlftpfs /usr/share/man/man1/curlftpfs.1.xz conflict with the package fuse-curlftpfs-0.9.2-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.; debug-ide-0.7.3-alt1.noarch rpm-filesystem-conflict-symlink-symlink warn value of symlink /usr/bin/rdebug-ide is different from the same symlink in the package ruby-debug-ide-0.7.3-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.; ; denemo-2.5.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.; denemo-2.5.0-alt1.x86_64 freedesktop-desktop info desktop-file-validate utility printed the following message(s): /usr/share/applications/denemo.desktop: hint: value item "GNOME" in key "Categories" in group "Desktop Entry" can be extended with another category among the following categories: GTK; /usr/share/applications/denemo.desktop: hint: value "GNOME;Audio;AudioVideo;Music;Education;" for key "Categories" in group "Desktop Entry" contains more than one main category; application might appear more than once in the application menu; /usr/share/applications/denemo.desktop: warning: value "Éditeur de partitions musicales" for key "Comment[fr]" in group "Desktop Entry" looks the same as that of key "GenericName[fr]"; dynflow-1.6.10-alt1.1.noarch systemd-but-no-native-init experimental The package have native systemd file(s) but no SysV init scripts. foreman-3.5.1-alt8.1.noarch systemd-but-no-native-init experimental The package have native systemd file(s) but no SysV init scripts. gem-aliyun-sdk-0.8.0-alt1.1.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/ruby/gemie/gems/aliyun-sdk-0.8.0/examples/aliyun/oss/object.rb: $ grep /tmp/ /usr/lib/ruby/gemie/gems/aliyun-sdk-0.8.0/examples/aliyun/oss/object.rb end # 上传一个文件 # 断点续传请参考:examples/resumable_upload.rb demo "Put object from local file" do File.open('/tmp/x', 'w'){ |f| f.write("hello world\n") } bucket.put_object('files/world', :file => '/tmp/x') puts "Put object: files/world" end # 创建一个Appendable object demo "Create appendable object" do puts "Total size: #{total_size}" end # 下载一个object:下载到文件中 demo "Get object to local file" do bucket.get_object('files/hello', :file => '/tmp/hello') puts "Get object: files/hello => /tmp/hello" end # 删除一个object demo "Delete object" do bucket.delete_object('files/world') -- :metas => {'year' => '2015', 'people' => 'mary'} ) do |content| content << 'hello world.' end o = bucket.get_object('files/hello', :file => '/tmp/x') puts "Object metas: #{o.metas}" end # 修改Object metas demo "Update object metas" do Found error in /usr/lib/ruby/gemie/gems/aliyun-sdk-0.8.0/examples/aliyun/oss/resumable_download.rb: $ grep -A5 -B5 /tmp/ /usr/lib/ruby/gemie/gems/aliyun-sdk-0.8.0/examples/aliyun/oss/resumable_download.rb puts end demo "Resumable download" do # 下载一个100M的文件 cpt_file = '/tmp/y.cpt' File.delete(cpt_file) if File.exist?(cpt_file) start = Time.now puts "Start download: resumable => /tmp/y" bucket.resumable_download( 'resumable', '/tmp/y', :cpt_file => cpt_file) do |progress| puts "Progress: #{(progress usr 100).round(2)} %" end puts "Download complete. Cost: #{Time.now - start} seconds." # 测试方法:; gem-bluecloth-devel-2.2.0-alt1.noarch rpm-filesystem-conflict-file-file warn File /usr/include/cstring.h conflicts with the package libsexpr-devel-1.3.1-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.; .; if conflicts are avoidable, consider using alternatives.; gem-cool-io-devel-1.7.1-alt1.noarch rpm-filesystem-conflict-file-file warn Files /usr/include/libev/ev.h /usr/include/libev/ev_vars.h /usr/include/libev/ev_wrap.h conflict with the package gem-nio4r-devel-2.5.8-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.; gem-foreman-hooks-0.3.17-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/lib/ruby/gemie/gems/foreman_hooks-0.3.17/examples/bash/log.sh: $ grep /tmp/ /usr/lib/ruby/gemie/gems/foreman_hooks-0.3.17/examples/bash/log.sh # Example of using hook_data to query the JSON representation of the object # passed by foreman_hooks. `cat $HOOK_OBJECT_FILE` to see the contents. hostname=$(hook_data host.name) echo "$(date): received ${event} on ${object}" >> /tmp/hook.log # exit code is important on orchestration tasks exit 0; gem-metaclass-0.0.4.1-alt1.noarch altlinux-policy-description-has-tags fail Description contains tags such as Provides/Requires/BuildRequires. Beware of errors with %ifs/%endifs!; gem-metaclass-0.0.4.1-alt1.noarch altlinux-policy-description-too-much-space info Description has 3 empty lines in a row. Format description properly. Beware of errors with %ifs/%endifs.; gem-msgpack-devel-1.5.6-alt1.noarch rpm-filesystem-conflict-file-file warn File /usr/include/msgpack/sysdep.h conflicts with the package libmsgpack-c-devel-6.0.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.; gem-nio4r-devel-2.5.8-alt1.noarch rpm-filesystem-conflict-file-file warn Files /usr/include/libev/ev.h /usr/include/libev/ev_vars.h /usr/include/libev/ev_wrap.h conflict with the package gem-cool-io-devel-1.7.1-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.; gem-rdiscount-devel-2.2.0.2-alt1.1.noarch rpm-filesystem-conflict-file-file warn There are file conflicts with the package gem-bluecloth-devel-2.2.0-alt1.noarch, for example, /usr/include/config.h (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.; gem-rmem-1.0.0-alt1.x86_64 missing-url info Missing Url: in a package.; gem-rmem-debuginfo-1.0.0-alt1.x86_64 missing-url info Missing Url: in a package.; gem-rmem-doc-1.0.0-alt1.noarch missing-url info Missing Url: in a package.; gem-ruby-libvirt-0.8.0-alt1.1.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/ruby/gemie/gems/ruby-libvirt-0.8.0/tests/test_storage.rb: $ grep /tmp/ /usr/lib/ruby/gemie/gems/ruby-libvirt-0.8.0/tests/test_storage.rb test.img 0 1 /tmp/rb-libvirt-test/test.img EOF new_storage_vol_xml_2 = < test2.img 0 5 /tmp/rb-libvirt-test/test2.img EOF # TESTGROUP: vol.pool expect_too_many_args(newpool, "delete", 1, 2) expect_invalid_arg_type(newpool, "delete", 'foo') expect_success(newpool, "no args", "delete") `mkdir -p /tmp/rb-libvirt-test` newpool.undefine `mkdir -p #{$POOL_PATH}` # TESTGROUP: pool.refresh; gem-unicode-devel-0.4.4.4-alt1.1.noarch rpm-filesystem-conflict-file-file warn File /usr/include/unicode/ustring.h conflicts with the package libicu-devel-7.4.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.; gimp-plugin-watermark-20230103-alt1.noarch missing-url info Missing Url: in a package.; gitlab-4.19.0-alt1.noarch rpm-filesystem-conflict-symlink-file warn symlink /usr/bin/gitlab is a file in the package python3-module-gitlab-4.4.0-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.; micmac-libann-devel-static-1.1.1-alt1.x86_64 rpm-filesystem-conflict-file-file warn File /usr/lib64/libANN.a conflicts with the package libann-devel-static-1.1.2-alt5.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.; mtest-3.6.0-alt1.noarch rpm-filesystem-conflict-symlink-file warn symlink /usr/bin/mtest is a file in the package parmetis-4.0.3-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.; nvm-0.39.3-alt1.noarch rpm-filesystem-conflict-file-file warn File /usr/share/zsh/site-functions/_nvm conflicts with the package zsh-completions-0.35.0-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.; pedump-0.6.5-alt1.noarch rpm-filesystem-conflict-symlink-file warn symlink /usr/bin/pedump is a file in the package mono-devel-6.12.0.199-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.; pgadmin4-8.3-alt2.noarch systemd-but-no-native-init experimental The package have native systemd file(s) but no SysV init scripts. pom-0.0.1-alt1.noarch rpm-filesystem-conflict-symlink-file warn symlink /usr/bin/pom is a file in the package bsd-games-2.17-alt3_71.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.; proxifier-1.0.3-alt2.noarch rpm-filesystem-conflict-symlink-symlink warn value of symlink /usr/bin/pruby is different from the same symlink in the package proxifier2-1.1.0-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.; proxifier2-1.1.0-alt1.noarch rpm-filesystem-conflict-symlink-symlink warn value of symlink /usr/bin/pruby is different from the same symlink in the package proxifier-1.0.3-alt2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; puppetdb-8.4.1-alt2.noarch systemd-but-no-native-init experimental The package have native systemd file(s) but no SysV init scripts. ruby-debug-ide-0.7.3-alt1.1.noarch rpm-filesystem-conflict-symlink-symlink warn value of symlink /usr/bin/rdebug-ide is different from the same symlink in the package debug-ide-0.7.3-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.; ; smart-proxy-3.5.1-alt3.1.noarch systemd-but-no-native-init experimental The package have native systemd file(s) but no SysV init scripts. utils-0.34.0-alt1.noarch rpm-filesystem-conflict-symlink-file warn symlink /usr/bin/enum is a file in the package enum-1.1-alt1_19.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.; ng alternatives.; utils-0.34.0-alt1.noarch rpm-filesystem-conflict-symlink-symlink warn value of symlink /usr/bin/edit is different from the same symlink in the package vi-traditional-4.1.3-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.; uuid-2.3.9-alt1.noarch rpm-filesystem-conflict-symlink-symlink warn value of symlink /usr/bin/uuid is different from the same symlink in the package ossp-uuid-1.6.2-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.; vim-plugin-rails-5.4-alt2.src specfile-macros-update_vimhelp-is-deprecated warn macros %update_vimhelp/%clean_vimhelp are deprecated and will be removed.; webdis-0.1.20-alt1.x86_64 systemd-but-no-native-init experimental The package have native systemd file(s) but no SysV init scripts.