Your message dated Mon, 31 Oct 2016 13:03:39 +0000 with message-id <e1c1cfx-0006ev...@fasolo.debian.org> and subject line Bug#837228: fixed in chef 12.14.60-1 has caused the Debian Bug report #837228, regarding chef: FTBFS: ERROR: Test "ruby2.3" failed. 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.) -- 837228: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837228 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Source: chef Version: 12.10.24-1 Severity: serious Tags: stretch sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20160910 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /usr/bin/ruby2.3 /usr/bin/gem2deb-test-runner > > ┌──────────────────────────────────────────────────────────────────────────────┐ > │ Checking Rubygems dependency resolution on ruby2.3 > │ > └──────────────────────────────────────────────────────────────────────────────┘ > > GEM_PATH=debian/ruby-chef-config/usr/share/rubygems-integration/all:debian/chef/usr/share/rubygems-integration/all:/var/lib/gems/2.3.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.3.0:/usr/share/rubygems-integration/2.3.0:/usr/share/rubygems-integration/all > ruby2.3 -e gem\ \"chef\" > /usr/lib/ruby/2.3.0/rubygems/dependency.rb:319:in `to_specs': Could not find > 'chef-zero' (~> 4.5) - did find: [chef-zero-5.0.0] (Gem::LoadError) > Checked in > 'GEM_PATH=debian/ruby-chef-config/usr/share/rubygems-integration/all:debian/chef/usr/share/rubygems-integration/all:/var/lib/gems/2.3.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.3.0:/usr/share/rubygems-integration/2.3.0:/usr/share/rubygems-integration/all', > execute `gem env` for more information > from /usr/lib/ruby/2.3.0/rubygems/specification.rb:1438:in `block in > activate_dependencies' > from /usr/lib/ruby/2.3.0/rubygems/specification.rb:1427:in `each' > from /usr/lib/ruby/2.3.0/rubygems/specification.rb:1427:in > `activate_dependencies' > from /usr/lib/ruby/2.3.0/rubygems/specification.rb:1409:in `activate' > from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_gem.rb:68:in `block > in gem' > from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_gem.rb:67:in > `synchronize' > from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_gem.rb:67:in `gem' > from -e:1:in `<main>' > bigdecimal (1.2.8) > bundler (1.12.5) > chef-config (12.10.24) > chef-zero (5.0.0) > cheffish (2.0.4) > compat_resource (12.10.5) > did_you_mean (1.0.0) > diff-lcs (1.2.5) > erubis (2.7.0) > ffi (1.9.10) > ffi-yajl (2.2.3) > fuzzyurl (0.8.0) > hashie (3.4.4) > highline (1.7.8) > io-console (0.4.5) > ipaddress (0.8.3) > json (1.8.3) > mime-types (2.6.1) > minitest (5.9.0) > mixlib-authentication (1.4.1) > mixlib-cli (1.5.0) > mixlib-config (2.2.1) > mixlib-log (1.6.0) > mixlib-shellout (2.2.6) > molinillo (0.5.0) > multi_json (1.11.2) > net-http-persistent (2.9.4) > net-scp (1.2.1) > net-sftp (2.1.2) > net-ssh (3.2.0) > net-ssh-gateway (1.2.0) > net-ssh-multi (1.2.1) > net-telnet (0.1.1) > ohai (8.10.0) > plist (3.2.0) > power_assert (0.2.7) > proxifier (1.0.3) > psych (2.0.17) > rack (1.6.4) > rake (10.5.0) > rdoc (4.2.1) > rspec (3.4.0) > rspec-core (3.4.3) > rspec-expectations (3.4.0) > rspec-its (1.2.0) > rspec-mocks (3.4.1) > rspec-support (3.4.1) > serverspec (2.18.0) > sigar (0.7.3) > specinfra (2.35.1) > syslog-logger (1.6.8) > systemu (2.6.5) > test-unit (3.1.7) > thor (0.19.1) > thread_order (1.1.0) > uuidtools (2.1.5) > ERROR: Test "ruby2.3" failed. The full build log is available from: http://aws-logs.debian.net/2016/09/10/chef_12.10.24-1_unstable.log (That DNS record was just updated. Use http://ec2-52-58-237-241.eu-central-1.compute.amazonaws.com if it doesn't work) A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---Source: chef Source-Version: 12.14.60-1 We believe that the bug you reported is fixed in the latest version of chef, 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 837...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Antonio Terceiro <terce...@debian.org> (supplier of updated chef 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: SHA256 Format: 1.8 Date: Mon, 31 Oct 2016 10:10:35 -0200 Source: chef Binary: chef ruby-chef-config Architecture: source Version: 12.14.60-1 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Extras Maintainers <pkg-ruby-extras-maintain...@lists.alioth.debian.org> Changed-By: Antonio Terceiro <terce...@debian.org> Description: chef - systems integration framework - clients ruby-chef-config - Chef configuration library Closes: 837228 Changes: chef (12.14.60-1) unstable; urgency=medium . * New upstream release - works with chef-zero 5.0 (Closes: #837228) - refresh patches - several updates to the list of dependencies - add patch to accept rspec 3.4 while it is not updated in Debian * debian/copyright: - update filename of windows gemspec in Files-Excluded * debian/ruby-tests.blacklist: add a few more tests to the blacklist; unfortunately I don't have the time to investigate the issues with them more deeply. * Added dependency on lsb-base for initscript Checksums-Sha1: 9bc3585517d0b14de9c01886b4254891c31d7cfb 2876 chef_12.14.60-1.dsc ecabade1fb3f8ed4c65c57b5a370b15854dcec4d 2275390 chef_12.14.60.orig.tar.gz e9e139c5205daae7aed94575c30e653804bab53e 28248 chef_12.14.60-1.debian.tar.xz Checksums-Sha256: 4d75a4e24f39764e2ada6dfa51009378ef0130e788de084fde80dc6b287a1837 2876 chef_12.14.60-1.dsc 6e1fe89c647cdc4687d488141c67cf97eb4eb6d1cc91ff924740e13d51125d1e 2275390 chef_12.14.60.orig.tar.gz ab6077f35a29cd202b618619f61953285ecd9b4d35b5985aac3e2a36ec3453dd 28248 chef_12.14.60-1.debian.tar.xz Files: 96897ead6790efcf875d2358f9aedfef 2876 ruby optional chef_12.14.60-1.dsc 3b4f03a29136a8d82f328a18710cfffc 2275390 ruby optional chef_12.14.60.orig.tar.gz 6ed88a94c77744797a0b271ae83ecb1b 28248 ruby optional chef_12.14.60-1.debian.tar.xz -----BEGIN PGP SIGNATURE----- iQIcBAEBCAAGBQJYFz9tAAoJEPwNsbvNRgvel0wP/2fpG2FsvYYk8Au2xjRSEDdQ NxuY7iNR08QH1FTJZizwl3A4pdJNUKI2wz/Dt21AdKC0FHK3QJdFvcxDz4MvHmdT ria07NPQKh/KUvqN03wsLW5AR5lhU1mPNRuyIRStgFsWA/fKo4pzJvC9e7HO5/FU OJl/C/5orVs9XjWwqS46rhjwkbN0NSLr68nVkj4orH42OVcmzXS6t1b7n9yx42LB gSevimQabOJEN/RG1OIm7gvJmzSleLJ50F8qUGqbZncqfOWbZ1ORciQ22kqiqYd+ CLR+8XKwplXrdUy02TfcR12RpZN2eU5AiKKLAA5y8aetPX4fACHfc3VZcyCEuTEB 0jwj9NcLKlYEDgn/3RYNNY9Rz4dAwlqauXIP0K2gzelSreGdXymG4giwomm0QV3Q lnr+LD9U3+fuScpo5aOXZWktbog+UK/ZLTiOdKoo2fFL8OEDjUk+joR3gaYKDu/8 G1F/C01Q9QfQ6GBEvhEMmTTV3TrcXPICkaMJ2N9gEeV5vmiJAHJZX1p+DE0L1JBk zFdXI29LOHau8cFcU4Ls+UGWOozDFYm7v33JT9F8DOHXyDEuif5HXyuq5qndAuFG 9bVYBlVQmcMNoBNfjaTcMA3S0Os5VjONPL6Y9KsRINg7KYMllNMot4OXJAC/EJ5o 3oKRXjazmLLS550TPMg3 =15il -----END PGP SIGNATURE-----
--- End Message ---
