| |
packager |
rpm id |
test |
status |
message |
 |
@ruby |
ruby-doc-html-3.3.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. |
|
majioa |
apache2-mod-passenger-6.0.23-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. |
 |
majioa |
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. |
 |
majioa |
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." # 测试方法： |
 |
majioa |
gem-cool-io-devel-1.8.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.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. |
|
majioa |
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! |
|
majioa |
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. |
|
majioa |
gem-msgpack-devel-1.7.2-alt1.noarch |
rpm-filesystem-conflict-file-file |
warn |
File /usr/include/msgpack/sysdep.h conflicts with the package libmsgpack-c-devel-6.1.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. |
|
majioa |
gem-nio4r-devel-2.7.3-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.8.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. |
|
majioa |
gem-racc-1.8.0-alt1.x86_64 |
buildroot |
fail |
found paths to buildroot: /etc/alternatives/packages.d/racc: /usr/bin/racc /usr/src/tmp/gem-racc-buildroot/usr/lib/ruby/gemie/gems/racc-1.8.0/bin/racc 100 |
|
majioa |
gem-rdiscount-devel-2.2.7.3-alt1.noarch |
rpm-filesystem-conflict-file-file |
warn |
There are file conflicts with the package gem-bluecloth-devel-2.2.0.2-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. |
|
majioa |
gem-ruby-libvirt-0.8.3-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/ruby/gemie/gems/ruby-libvirt-0.8.3/tests/test_storage.rb: $ grep /tmp/ /usr/lib/ruby/gemie/gems/ruby-libvirt-0.8.3/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_invalid_arg_type(newpool, "delete", 'foo') expect_success(newpool, "no args", "delete") if !test_default_uri? `mkdir -p /tmp/rb-libvirt-test` end newpool.undefine if !test_default_uri? Found error in /usr/lib/ruby/gemie/gems/ruby-libvirt-0.8.3/examples/storage.rb: $ grep -A5 -B5 /tmp/ /usr/lib/ruby/gemie/gems/ruby-libvirt-0.8.3/examples/storage.rb # etc. See https://libvirt.org/formatstorage.html for more details require 'libvirt' # a directory storage pool. This will be a pool with the name # 'ruby-libvirt-tester' with the pool itself in /tmp/ruby-libvirt-tester storage_pool_xml = < ruby-libvirt-tester 33a5c045-645a-2c00-e56b-927cdf34e17a /tmp/ruby-libvirt-tester EOF # a storage volume. This will have name test.img, with capacity of 1GB -- test.img 0 1 /tmp/ruby-libvirt-tester/test.img EOF # open up the connection to libvirt |
|
majioa |
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. |
|
majioa |
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.206-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. |
|
majioa |
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. |
|
majioa |
smart-proxy-3.5.1-alt3.3.noarch |
sisyphus_check |
fail |
sisyphus_check failed: /ALT/Sisyphus/files/noarch/RPMS/smart-proxy-3.5.1-alt3.3.noarch.rpm: Invalid path names: /usr/lib/tmpfiles.d/smart-proxy.conf sisyphus_check: check-fhs ERROR: FHS violation |
|
majioa |
smart-proxy-3.5.1-alt3.3.noarch |
systemd-but-no-native-init |
experimental |
The package have native systemd file(s) but no SysV init scripts. |
|
nbr |
pcs-0.11.6-alt2.x86_64 |
init-condrestart |
fail |
/etc/rc.d/init.d/pcsd: missing condstop target. ERROR: alt-specific script %_sbindir/preun_service (used in your %preun_service macro) depends on condstop. Please, fix. |
|
nbr |
python3-module-snmp-0.11.6-alt2.x86_64 |
systemd-but-no-native-init |
experimental |
The package have native systemd file(s) but no SysV init scripts. |