[DRE-maint] Bug#1150361: vagrant: FTBFS: raise Errors::BoxMetadataDownloadError,

Santiago Vila sanvila at debian.org
Fri Oct 9 00:00:57 BST 2026


Package: src:vagrant
Version: 2.3.7+git20230731.5fc64cde+dfsg-4.1
Severity: serious
Tags: ftbfs forky sid

Dear maintainer:

During a rebuild of all packages in unstable, this package failed to build.

Below you will find the last part of the build log (probably the most
relevant part, but not necessarily). If required, the full build log
is available here:

https://people.debian.org/~sanvila/build-logs/202610/

About the archive rebuild: The build was made on virtual machines from AWS,
using sbuild and a reduced chroot with only build-essential packages.

If you cannot reproduce the bug please contact me privately, as I
am willing to provide ssh access to a virtual machine where the bug is
fully reproducible.

If this is really a bug in one of the build-depends, please use
reassign and add an affects on src:vagrant, so that this is still
visible in the BTS web page for this package.

Thanks.

--------------------------------------------------------------------------------
[...]

Failures:

  1) VagrantPlugins::CommandBox::Command::Update execute updating specific box download options are specified passes down download options
     Failure/Error:
       raise Errors::BoxMetadataDownloadError,
         message: e.extra_data[:message]
     
     Vagrant::Errors::BoxMetadataDownloadError:
       There was an error while downloading the metadata for this box.
       The error message is shown below:
     
       curl: The file 'foo' provided to --cacert does not exist
       curl: option --cacert: is badly used here
       curl: try 'curl --help' or 'curl --manual' for more information
     # /<<PKGBUILDDIR>>/lib/vagrant/box.rb:164:in `rescue in load_metadata'
     # /<<PKGBUILDDIR>>/lib/vagrant/box.rb:163:in `load_metadata'
     # /<<PKGBUILDDIR>>/lib/vagrant/box.rb:194:in `has_update?'
     # /<<PKGBUILDDIR>>/plugins/commands/box/command/update.rb:147:in `box_update'
     # /<<PKGBUILDDIR>>/plugins/commands/box/command/update.rb:88:in `block in update_specific'
     # /<<PKGBUILDDIR>>/plugins/commands/box/command/update.rb:86:in `each'
     # /<<PKGBUILDDIR>>/plugins/commands/box/command/update.rb:86:in `update_specific'
     # /<<PKGBUILDDIR>>/plugins/commands/box/command/update.rb:47:in `execute'
     # /<<PKGBUILDDIR>>/test/unit/plugins/commands/box/command/update_test.rb:234:in `block (5 levels) in <top (required)>'
     # ------------------
     # --- Caused by: ---
     # Vagrant::Errors::DownloaderError:
     #   An error occurred while downloading the remote file. The error
     #   message, if any, is reproduced below. Please fix this error and try
     #   again.
     #   
     #   curl: The file 'foo' provided to --cacert does not exist
     #   curl: option --cacert: is badly used here
     #   curl: try 'curl --help' or 'curl --manual' for more information
     #   /<<PKGBUILDDIR>>/lib/vagrant/util/downloader.rb:230:in `execute_curl'

Finished in 4 minutes 6.1 seconds (files took 1.11 seconds to load)
3053 examples, 1 failure, 15 pending

Failed examples:

rspec /<<PKGBUILDDIR>>/test/unit/plugins/commands/box/command/update_test.rb:198 # VagrantPlugins::CommandBox::Command::Update execute updating specific box download options are specified passes down download options

/usr/bin/ruby3.3 -I/usr/share/rubygems-integration/all/gems/rspec-support-3.13.7/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.13.6/lib /usr/share/rubygems-integration/all/gems/rspec-core-3.13.6/exe/rspec --pattern test/unit/\{plugins\}/\*\*/\*_test.rb  --exclude-pattern \{test/unit/vagrant/action/builtin/box_add_test.rb,test/unit/plugins/communicators/winrm/\*_test.rb,test/unit/plugins/pushes/ftp/\*_test.rb,test/unit/plugins/commands/serve/mappers_test.rb\} -I/<<PKGBUILDDIR>>/debian/lib failed
/usr/lib/ruby/vendor_ruby/gem2deb.rb:52:in `run': /usr/bin/ruby3.3 /usr/bin/gem2deb-test-runner (Gem2Deb::CommandFailed)
	from /usr/lib/ruby/vendor_ruby/gem2deb.rb:64:in `block in run_ruby'
	from /usr/lib/ruby/vendor_ruby/gem2deb.rb:87:in `maybe_crossbuild'
	from /usr/lib/ruby/vendor_ruby/gem2deb.rb:63:in `run_ruby'
	from /usr/lib/ruby/vendor_ruby/gem2deb/dh_ruby.rb:189:in `run_tests_for_version'
	from /usr/lib/ruby/vendor_ruby/gem2deb/dh_ruby.rb:176:in `block in run_tests'
	from /usr/lib/ruby/vendor_ruby/gem2deb/dh_ruby.rb:175:in `each'
	from /usr/lib/ruby/vendor_ruby/gem2deb/dh_ruby.rb:175:in `run_tests'
	from /usr/lib/ruby/vendor_ruby/gem2deb/dh_ruby.rb:71:in `run_tests'
	from /usr/lib/ruby/vendor_ruby/gem2deb/dh_ruby.rb:57:in `install'
	from /usr/lib/ruby/vendor_ruby/gem2deb/dh_ruby.rb:163:in `install'
	from /usr/bin/dh_ruby:89:in `<main>'
dh_auto_install: error: dh_ruby --install /<<BUILDDIR>>/vagrant-2.3.7\+git20230731.5fc64cde\+dfsg/debian/vagrant returned exit code 1
make[1]: *** [debian/rules:16: override_dh_auto_install] Error 25
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
make: *** [debian/rules:9: binary] Error 2
dpkg-buildpackage: error: debian/rules binary subprocess failed with exit status 2
--------------------------------------------------------------------------------



More information about the Pkg-ruby-extras-maintainers mailing list