[DRE-maint] Bug#954706: vagrant: FTBFS: Failed to load /dev/null because it doesn't contain valid YAML hash
Lucas Nussbaum
lucas at debian.org
Sun Mar 22 13:58:50 GMT 2020
Source: vagrant
Version: 2.2.6+dfsg-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200322 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<<PKGBUILDDIR>>'
> Unsupported VirtualBox: >= 6.2
> dh_auto_install
> dh_ruby --install /<<BUILDDIR>>/vagrant-2.2.6\+dfsg/debian/vagrant
> dh_ruby --install
> /usr/bin/ruby2.7 -S gem build --config-file /dev/null --verbose /tmp/d20200322-27815-1sjd7w0/gemspec
> Failed to load /dev/null because it doesn't contain valid YAML hash
> WARNING: open-ended dependency on bcrypt_pbkdf (>= 0) is not recommended
> use a bounded requirement, such as '~> x.y'
> WARNING: open-ended dependency on childprocess (>= 0) is not recommended
> use a bounded requirement, such as '~> x.y'
> WARNING: open-ended dependency on ed25519 (>= 0) is not recommended
> use a bounded requirement, such as '~> x.y'
> WARNING: open-ended dependency on erubis (>= 0) is not recommended
> use a bounded requirement, such as '~> x.y'
> WARNING: open-ended dependency on i18n (>= 0) is not recommended
> use a bounded requirement, such as '~> x.y'
> WARNING: open-ended dependency on listen (>= 0) is not recommended
> use a bounded requirement, such as '~> x.y'
> WARNING: open-ended dependency on log4r (>= 0) is not recommended
> use a bounded requirement, such as '~> x.y'
> WARNING: open-ended dependency on net-ssh (>= 0) is not recommended
> use a bounded requirement, such as '~> x.y'
> WARNING: open-ended dependency on net-sftp (>= 0) is not recommended
> use a bounded requirement, such as '~> x.y'
> WARNING: open-ended dependency on net-scp (>= 0) is not recommended
> use a bounded requirement, such as '~> x.y'
> WARNING: open-ended dependency on rest-client (>= 0) is not recommended
> use a bounded requirement, such as '~> x.y'
> WARNING: open-ended dependency on rubyzip (>= 0) is not recommended
> use a bounded requirement, such as '~> x.y'
> WARNING: open-ended dependency on vagrant_cloud (>= 0) is not recommended
> use a bounded requirement, such as '~> x.y'
> WARNING: See http://guides.rubygems.org/specification-reference/ for help
> Successfully built RubyGem
> Name: vagrant
> Version: 2.2.6
> File: vagrant-2.2.6.gem
> /usr/bin/ruby2.7 -S gem install --config-file /dev/null --verbose --local --verbose --no-document --ignore-dependencies --install-dir debian/vagrant/usr/share/rubygems-integration/all /tmp/d20200322-27815-1sjd7w0/vagrant-2.2.6.gem
> Failed to load /dev/null because it doesn't contain valid YAML hash
> ERROR: Error installing /tmp/d20200322-27815-1sjd7w0/vagrant-2.2.6.gem:
> vagrant requires Ruby version ~> 2.4, < 2.7. The current ruby version is 2.7.0.0.
> /usr/lib/ruby/vendor_ruby/gem2deb.rb:56:in `run': /usr/bin/ruby2.7 -S gem install --config-file /dev/null --verbose --local --verbose --no-document --ignore-dependencies --install-dir debian/vagrant/usr/share/rubygems-integration/all /tmp/d20200322-27815-1sjd7w0/vagrant-2.2.6.gem (Gem2Deb::CommandFailed)
> from /usr/lib/ruby/vendor_ruby/gem2deb/gem_installer.rb:188:in `run_gem'
> from /usr/lib/ruby/vendor_ruby/gem2deb/gem_installer.rb:103:in `block in install_files_and_build_extensions'
> from /usr/lib/ruby/vendor_ruby/gem2deb/gem_installer.rb:51:in `each'
> from /usr/lib/ruby/vendor_ruby/gem2deb/gem_installer.rb:51:in `install_files_and_build_extensions'
> from /usr/lib/ruby/vendor_ruby/gem2deb/dh_ruby.rb:84:in `block in install'
> from /usr/lib/ruby/vendor_ruby/gem2deb/dh_ruby.rb:82:in `each'
> from /usr/lib/ruby/vendor_ruby/gem2deb/dh_ruby.rb:82:in `install'
> from /usr/bin/dh_ruby:94:in `<main>'
> dh_auto_install: error: dh_ruby --install /<<BUILDDIR>>/vagrant-2.2.6\+dfsg/debian/vagrant returned exit code 1
> make[1]: *** [debian/rules:16: override_dh_auto_install] Error 25
The full build log is available from:
http://qa-logs.debian.net/2020/03/22/vagrant_2.2.6+dfsg-2_unstable.log
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.
More information about the Pkg-ruby-extras-maintainers
mailing list