Your message dated Tue, 06 Feb 2018 18:35:57 +0000 with message-id <e1ej861-0002uf...@fasolo.debian.org> and subject line Bug#888160: fixed in ruby-memfs 1.0.0-1 has caused the Debian Bug report #888160, regarding ruby-memfs: FTBFS on ruby2.5: No such file or directory - /test-file to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 888160: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888160 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Source: ruby-memfs Version: 0.5.0-1 Severity: important User: debian-r...@lists.debian.org Usertags: ruby2.5 Dear Maintainer, This package fails to build against ruby2.5. Soon, there will be a transition to ruby2.5, and this package will FTBFS in sid. There may be some details on the wiki about common problems: https://wiki.debian.org/Teams/Ruby/Ruby25Transition Build log excerpt: Failures: 1) FileUtils.copy_entry when +src+ does not exist raises an exception Failure/Error: find(path) || fail(Errno::ENOENT, path) Errno::ENOENT: No such file or directory - /test-file # ./lib/memfs/file_system.rb:64:in `find!' # ./lib/memfs/file/stat.rb:56:in `initialize' # ./lib/memfs/file.rb:137:in `new' # ./lib/memfs/file.rb:137:in `lstat' # ./spec/fileutils_spec.rb:300:in `block (5 levels) in <top (required)>' # ./spec/spec_helper.rb:21:in `block (2 levels) in <top (required)>' # ./spec/fileutils_spec.rb:299:in `block (4 levels) in <top (required)>' 2) FileUtils.rm_f calls rm with +:force+ set to true Failure/Error: described_class.rm_f('test') TypeError: superclass mismatch for class File # ./spec/fileutils_spec.rb:886:in `block (3 levels) in <top (required)>' 3) FileUtils.rm_rf calls rm with +:force+ set to true Failure/Error: described_class.rm_rf('test') TypeError: superclass mismatch for class File # ./spec/fileutils_spec.rb:921:in `block (3 levels) in <top (required)>' 4) FileUtils.rmdir when a directory is not empty ignores errors Failure/Error: expect { described_class.rmdir('/test-dir') }.not_to raise_error TypeError: superclass mismatch for class File # ./spec/fileutils_spec.rb:946:in `block (4 levels) in <top (required)>' 5) FileUtils.rmdir when a directory is not empty doesn't remove the directory Failure/Error: fail Errno::ENOTEMPTY, path unless directory.empty? Errno::ENOTEMPTY: Directory not empty - /test-dir # ./lib/memfs/file_system.rb:121:in `rmdir' # ./lib/memfs/dir.rb:84:in `rmdir' # ./spec/fileutils_spec.rb:950:in `block (4 levels) in <top (required)>' Finished in 0.47079 seconds (files took 1.03 seconds to load) 784 examples, 5 failures, 7 pending Failed examples: rspec ./spec/fileutils_spec.rb:298 # FileUtils.copy_entry when +src+ does not exist raises an exception rspec ./spec/fileutils_spec.rb:884 # FileUtils.rm_f calls rm with +:force+ set to true rspec ./spec/fileutils_spec.rb:919 # FileUtils.rm_rf calls rm with +:force+ set to true rspec ./spec/fileutils_spec.rb:945 # FileUtils.rmdir when a directory is not empty ignores errors rspec ./spec/fileutils_spec.rb:949 # FileUtils.rmdir when a directory is not empty doesn't remove the directory [33m[Coveralls] Outside the CI environment, not sending data.[0m /usr/bin/ruby2.5 /usr/bin/rspec --pattern ./spec/\*\*/\*_spec.rb --format documentation failed ERROR: Test "ruby2.5" failed. Exiting. dh_auto_install: dh_ruby --install /build/ruby-memfs-0.5.0/debian/ruby-memfs returned exit code 1 debian/rules:6: recipe for target 'binary' failed make: *** [binary] Error 1 dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2 Full build log: https://rbuild.fau.xxx/2018-01-23/ruby-memfs.log Please fix it! Cheers, Chris.
--- End Message ---
--- Begin Message ---Source: ruby-memfs Source-Version: 1.0.0-1 We believe that the bug you reported is fixed in the latest version of ruby-memfs, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 888...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sebastien Badia <sba...@debian.org> (supplier of updated ruby-memfs package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Format: 1.8 Date: Tue, 06 Feb 2018 16:21:20 +0100 Source: ruby-memfs Binary: ruby-memfs Architecture: source Version: 1.0.0-1 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Extras Maintainers <pkg-ruby-extras-maintain...@lists.alioth.debian.org> Changed-By: Sebastien Badia <sba...@debian.org> Description: ruby-memfs - MemFs provides an in-memory fake file system that can be used for Closes: 888160 Changes: ruby-memfs (1.0.0-1) unstable; urgency=medium . [ Cédric Boutillier ] * Use https:// in Vcs-* fields * Run wrap-and-sort on packaging files . [ Sebastien Badia ] * New upstream version 1.0.0 * Use HTTPS for homepage, watch and copyright URI * d/patches: Import upstream fix for tests on Ruby 2.5 (Closes: #888160) * d/compat: Bump compat version to 10 * d/control: + Bump to Standards-Version 4.1.3 (no changes needed) + Use my Debian email address Checksums-Sha1: d470f49c13b3feacae1177bae3062188247b4457 2059 ruby-memfs_1.0.0-1.dsc 6f4d88958498ee4c9518cddfb03d8b99c6d5ca89 43274 ruby-memfs_1.0.0.orig.tar.gz a39f5c7cd074f02311b752bb7c6900e163b3140e 3556 ruby-memfs_1.0.0-1.debian.tar.xz 4c34a0e2edf3c3d22fdf393856643721871bf2a0 6778 ruby-memfs_1.0.0-1_source.buildinfo Checksums-Sha256: 7aa170ee9fb7e509e2e284136a4002a11a0fc86ea1f8ffd0a6ea558e9b2989db 2059 ruby-memfs_1.0.0-1.dsc 612cda1051e8f72a5a14dc9d722ba42148a9a93eeeda6a1b9079eade3dbf8167 43274 ruby-memfs_1.0.0.orig.tar.gz b7c522e7a36b52a559822cc84920970eb40a881705d55b0d88cdcd30613050b7 3556 ruby-memfs_1.0.0-1.debian.tar.xz b4fc27612fb92d31b0bbe42a77fcc7c19973894d6d3b3c73aaf3d23d43d18682 6778 ruby-memfs_1.0.0-1_source.buildinfo Files: 7fb0b304d6edeb760ff5a34516dfcf5b 2059 ruby optional ruby-memfs_1.0.0-1.dsc bda85da1c997de4739fff7bf165246af 43274 ruby optional ruby-memfs_1.0.0.orig.tar.gz 9098ae18abffa161dfc66846d5ecb939 3556 ruby optional ruby-memfs_1.0.0-1.debian.tar.xz e66d2775395bb34ed6bd2e4191368b4c 6778 ruby optional ruby-memfs_1.0.0-1_source.buildinfo -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEfkPprL9yerPPCIUzhxbORhSkUtgFAlp58HcACgkQhxbORhSk UtjQTg/9HqKrmNmdBbt5LXj3qnjpSCHF5yRgmrOxr89RYVhgmAJaJGe7AFsfQarJ wn9AZXGhlE96lxoHjkR7cNulaJu/zP2Dd+PyQDwM94R2fvmiACpOXC1lFCkCrynH ArUcGEW/z27EvazeLsdjxGeRFaHM/FGRvWjtk8VRQkKuWG6gVOPKu2gmTRLK9zoM cBXRq8jgPp/2Mu1d/gZGIH1NMlzBiT7MspAHNWQoP5kP7FMzOGMQthxDVnk69kfb 2PytM3mk3l7KnYITz5h+yrT/h8x0TdlLDXfY5VUiEv2AIr92xnM1fAgHbmptFO23 GJvpwre5xgMsiWA2SOxplv8lKJ7wgipt3aD47Xd7/7uLS2uJpEu5FjhRlgWvhUkg anIifKfYtfyA+hUHo5ugzihYkzjbzCyMCmbdWJs/vR7ijYDwsTAS+hv3RTB1kqXn GInWy9ZQT04Cpg2d1FwpviTogzasFo/7/zhNgCQDlEMZA4o4JWTh+8xcskuWJ7Fe VV7qeQd5s9WEv09q4pxdcSb+Hwn/MFq/boTWOP1l5wvFAjyQi4DZ0w9ti+Fpf1BL EE0tLjqCrnWaMo+y1oIdAMI/C+YOL67/YO7jV09t/j9bvVhRVEhUTLlfcndufz1z x32gvSHq6slz3ZvWMzK0TWVplEHlSqpu8BU4bw91ZFFIfZnO4NM= =4j7X -----END PGP SIGNATURE-----
--- End Message ---
