Your message dated Sat, 10 Feb 2018 21:22:02 +0000
with message-id <e1ekcaw-000enb...@fasolo.debian.org>
and subject line Bug#888185: fixed in rubocop 0.52.1+dfsg-1
has caused the Debian Bug report #888185,
regarding rubocop: FTBFS on ruby2.5: Error: FileUtils.rmdir(attack_target_dir)
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.)


-- 
888185: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888185
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rubocop
Version: 0.51.0+dfsg-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) RuboCop::ResultCache cached result that was saved with no command line 
option when no option is given when a symlink is present in the cache location 
and symlink attack protection is disabled permits caching and prints no warning
     Failure/Error: FileUtils.rmdir(attack_target_dir)

     Errno::ENOTEMPTY:
       Directory not empty @ dir_s_rmdir - /tmp/d20180123-1310-1kp5vxe
     # /build/rubocop-0.51.0+dfsg/spec/rubocop/result_cache_spec.rb:95:in 
`block (5 levels) in <top (required)>'
     # /build/rubocop-0.51.0+dfsg/lib/rubocop/rspec/shared_contexts.rb:27:in 
`block (4 levels) in <top (required)>'
     # /build/rubocop-0.51.0+dfsg/lib/rubocop/rspec/shared_contexts.rb:26:in 
`chdir'
     # /build/rubocop-0.51.0+dfsg/lib/rubocop/rspec/shared_contexts.rb:26:in 
`block (3 levels) in <top (required)>'
     # /build/rubocop-0.51.0+dfsg/lib/rubocop/rspec/shared_contexts.rb:8:in 
`block (2 levels) in <top (required)>'

Finished in 33.85 seconds (files took 3.52 seconds to load)
17503 examples, 1 failure, 1 pending

Failed examples:

rspec /build/rubocop-0.51.0+dfsg/spec/rubocop/result_cache_spec.rb:121 # 
RuboCop::ResultCache cached result that was saved with no command line option 
when no option is given when a symlink is present in the cache location and 
symlink attack protection is disabled permits caching and prints no warning

Randomized with seed 48248

/usr/bin/ruby2.5 /usr/bin/rspec --pattern ./spec/\*\*/\*_spec.rb failed
ERROR: Test "ruby2.5" failed. Exiting.
dh_auto_install: dh_ruby --install /build/rubocop-0.51.0\+dfsg/debian/rubocop 
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/rubocop.log

Please fix it!

Cheers,
Chris.

--- End Message ---
--- Begin Message ---
Source: rubocop
Source-Version: 0.52.1+dfsg-1

We believe that the bug you reported is fixed in the latest version of
rubocop, 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 rubocop 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: Sat, 10 Feb 2018 18:22:05 +0100
Source: rubocop
Binary: rubocop
Architecture: source
Version: 0.52.1+dfsg-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:
 rubocop    - Ruby static code analyzer
Closes: 888185
Changes:
 rubocop (0.52.1+dfsg-1) unstable; urgency=medium
 .
   * New upstream version 0.52.1+dfsg
     + Fix FTBFS, support for Ruby 2.5 added upstream (Closes: #888185)
   * d/compat: Bump compat version to 11
   * d/control:
     + Bump to Standards-Version 4.1.3 (no changes needed)
     + Added pry and rubocop-rspec to build-deps
   * d/patches:
     + Refresh Debian patches (new upstream)
     + Update series (patch-file-present-but-not-mentioned-in-series)
Checksums-Sha1:
 6bd484b2084e33dcfcd825fd046ce99f3a52ded1 2281 rubocop_0.52.1+dfsg-1.dsc
 c5e60cad04f384c9a82732c860a16866f8632223 946989 rubocop_0.52.1+dfsg.orig.tar.gz
 51085d6eea5e576ab70e3c774e320407c0d8ce62 10108 
rubocop_0.52.1+dfsg-1.debian.tar.xz
 6db4a9c3ef3ea693874f9e16eaa33677595db2f4 7919 
rubocop_0.52.1+dfsg-1_source.buildinfo
Checksums-Sha256:
 9dc5b8997053cef155f47f5ca6f6637f72c851a4c5f27fe346b8c5f0108cf5be 2281 
rubocop_0.52.1+dfsg-1.dsc
 297b2eec8d527369c5a1ef94c8b3ec2464a94a78f6e2918b48471930dea88b7c 946989 
rubocop_0.52.1+dfsg.orig.tar.gz
 14079ab7257898ae9e6d080ab1e888b9692f161509b35730ae841d2e87159bba 10108 
rubocop_0.52.1+dfsg-1.debian.tar.xz
 9879e6965ce0d22739c10e0bf735727fcc1208b209588872e61b1f5595d3fc52 7919 
rubocop_0.52.1+dfsg-1_source.buildinfo
Files:
 b77e853ddede3f994db97c10e35a28a3 2281 ruby optional rubocop_0.52.1+dfsg-1.dsc
 423110e4badefdb6695e74638227da81 946989 ruby optional 
rubocop_0.52.1+dfsg.orig.tar.gz
 0dfa1ca8e289bc5f2da88c0e9657a464 10108 ruby optional 
rubocop_0.52.1+dfsg-1.debian.tar.xz
 564b7866eebf206f1a0ff2fef895ee5d 7919 ruby optional 
rubocop_0.52.1+dfsg-1_source.buildinfo

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEfkPprL9yerPPCIUzhxbORhSkUtgFAlp/VZ8ACgkQhxbORhSk
UthUyg//adMnqXCzJ1HImqBKrmmk98tYJ1i1r8NxhC15xLzlXD9tavpz/UlK6YAh
5HDNzyyNIhrsor2PgVkwGFEmoLV4UcUXuZnFsAn/4dx2hsp4Uetp+zmThFCdclsC
MOuexEloc03Ly1sRlA4nH4vrrh2RRASr8Ky40gzcPHa3GywTheNS4MjEw7oKKKRD
hZ5ktnUcKhpjgMIpZOR9wuDU7a2AkNMar1qKFGEb6P7dXBYGOzoil7zXSx0zg/kz
d6SsP4t4euafSqSu60Px/unsGVt2woYpqoEzFVMiNruhBX0xi/vmtgiH7DseXF7X
dX9aeTdT9OGcNdSAiqhG1ozY/NJy4Lgvh2bdzEkLZHk+qaZ6mcXSW1entZwxtQ6Q
ehlIaNo/xkPrh9ZE8dT/d4wdp1wUpRdtJ6RvyXK4O3bjOwKjp9CL3raqAnU2gSqA
rRhIz+txIhQqQCgBv5qBm02LQNpYBBSqnHY/zpArUf2fZyjUbhk8UGynmeTeoHGO
XPEZMtbIec1PUwRJJI90uITiTLwr0lNiKqhaN2jw1CE+KDna3zAnuYn25+sFOtLq
bVMMiL6KHTJtV9Jcha2unyBqW5L5L+je8v9GjcE0G0QAAJiDHem8+P2ESXfbC365
WJ273HHSUNpsoSnJ3xTZn7s/IqAllfVYOyNTlPznCbTJK2j54SI=
=JnAn
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to