Your message dated Mon, 15 Nov 2021 12:48:51 +0000
with message-id <e1mmbpn-000h0b...@fasolo.debian.org>
and subject line Bug#996529: fixed in vagrant 2.2.19+dfsg-1
has caused the Debian Bug report #996529,
regarding vagrant: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed:
RuntimeError:
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.)
--
996529: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996529
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: vagrant
Version: 2.2.14+dfsg-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-r...@lists.debian.org
Usertags: ruby3.0
Hi,
We are about to enable building against ruby3.0 on unstable. During a test
rebuild, vagrant was found to fail to build in that situation.
To reproduce this locally, you need to install ruby-all-dev from experimental
on an unstable system or build chroot.
Relevant part (hopefully):
> RuntimeError:
> class variable access from toplevel
> #
> /<<PKGBUILDDIR>>/test/unit/plugins/synced_folders/unix_mount_helpers_test.rb:10:in
> `block (3 levels) in <top (required)>'
> #
> /<<PKGBUILDDIR>>/test/unit/plugins/synced_folders/unix_mount_helpers_test.rb:9:in
> `initialize'
> #
> /<<PKGBUILDDIR>>/test/unit/plugins/synced_folders/unix_mount_helpers_test.rb:9:in
> `new'
> #
> /<<PKGBUILDDIR>>/test/unit/plugins/synced_folders/unix_mount_helpers_test.rb:9:in
> `block (2 levels) in <top (required)>'
> #
> /<<PKGBUILDDIR>>/test/unit/plugins/synced_folders/unix_mount_helpers_test.rb:34:in
> `block (4 levels) in <top (required)>'
>
> Finished in 14 minutes 32 seconds (files took 5.03 seconds to load)
> 2824 examples, 7 failures, 9 pending
>
> Failed examples:
>
> rspec
> /<<PKGBUILDDIR>>/test/unit/plugins/commands/cloud/provider/upload_test.rb:88
> #
> VagrantPlugins::CloudCommand::ProviderCommand::Command::Upload#upload_provider
> with direct option should use direct upload
> rspec /<<PKGBUILDDIR>>/test/unit/plugins/commands/cloud/search_test.rb:59 #
> VagrantPlugins::CloudCommand::Command::Search#search with valid options
> should use options when performing search
> rspec /<<PKGBUILDDIR>>/test/unit/plugins/commands/cloud/search_test.rb:72 #
> VagrantPlugins::CloudCommand::Command::Search#search with valid options with
> invalid options should only pass supported options to search
> rspec /<<PKGBUILDDIR>>/test/unit/plugins/kernel_v2/config/disk_test.rb:120 #
> VagrantPlugins::Kernel_V2::VagrantConfigDisk#add_provider_config normalizes
> provider config
> rspec
> /<<PKGBUILDDIR>>/test/unit/plugins/synced_folders/unix_mount_helpers_test.rb:21
> # VagrantPlugins::SyncedFolder::UnixMountHelpers.merge_mount_options with no
> override should split options into individual options
> rspec
> /<<PKGBUILDDIR>>/test/unit/plugins/synced_folders/unix_mount_helpers_test.rb:28
> # VagrantPlugins::SyncedFolder::UnixMountHelpers.merge_mount_options with
> overrides should merge all options
> rspec
> /<<PKGBUILDDIR>>/test/unit/plugins/synced_folders/unix_mount_helpers_test.rb:33
> # VagrantPlugins::SyncedFolder::UnixMountHelpers.merge_mount_options with
> overrides should override options defined in base
>
> /usr/bin/ruby3.0
> -I/usr/share/rubygems-integration/all/gems/rspec-support-3.9.3/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib
> /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/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\}
> -I/<<PKGBUILDDIR>>/debian/lib failed
> ERROR: Test "ruby3.0" failed:
The full build log is available at
https://people.debian.org/~kanashiro/ruby3.0/round2/builds/3/vagrant/vagrant_2.2.14+dfsg-1+rebuild1633400150_amd64.build.txt
signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: vagrant
Source-Version: 2.2.19+dfsg-1
Done: Antonio Terceiro <terce...@debian.org>
We believe that the bug you reported is fixed in the latest version of
vagrant, 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 996...@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 vagrant 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, 15 Nov 2021 09:10:33 -0300
Source: vagrant
Architecture: source
Version: 2.2.19+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Team
<pkg-ruby-extras-maintain...@lists.alioth.debian.org>
Changed-By: Antonio Terceiro <terce...@debian.org>
Closes: 996529
Changes:
vagrant (2.2.19+dfsg-1) unstable; urgency=medium
.
* New upstream version 2.2.19+dfsg
- Passes tests against ruby3.0 with ruby-rspec >= 3.10 (Closes: #996529)
* debian/upstream/metadata: correct URLs
* debian/control: refresh build dependencies
* Bump Standards-Version to 4.6.0; no changes needed
* Refresh patches
* Refresh packaging files from dh-make-ruby
* debian/rules: replace whitelist/blacklist with include/exclude
* System-side installed plugins: cope with upstream changes
* autopkgtest: integration-test: add missing dependency on dnsmaq
* autopkgtest: integration-test: add missing dependency on sudo
Checksums-Sha1:
8c64350702e0e087df90cb864923a2b208ed4642 2615 vagrant_2.2.19+dfsg-1.dsc
9e67b1f45a4bc8aec570f188b74a1dcd01d323ad 707664 vagrant_2.2.19+dfsg.orig.tar.xz
a8a952f567d205f741a9ca17e99493b4bbe02e71 15224
vagrant_2.2.19+dfsg-1.debian.tar.xz
32dd0bdfc5edf6a2ecf302353701c500ff0817dd 10388
vagrant_2.2.19+dfsg-1_amd64.buildinfo
Checksums-Sha256:
c584bc8461b0b224d05d4f1ef08220f3ef3431af515ae9042d1b2ec08e9d5a20 2615
vagrant_2.2.19+dfsg-1.dsc
6b5a47bd83e2475c6710c0c97ed588519e0e6bd5dda75db4fded52262f1468f1 707664
vagrant_2.2.19+dfsg.orig.tar.xz
587a33f6f8de81b4b18fe74edf4695b58a5f22bd4574c59adbc4f6ab8919cfe6 15224
vagrant_2.2.19+dfsg-1.debian.tar.xz
d8c57c44cce3df616b454ee3a5ef73a7f99ae97f97612d2555d9417666a86097 10388
vagrant_2.2.19+dfsg-1_amd64.buildinfo
Files:
39037c7d53264cf296380c333a13c7b4 2615 admin optional vagrant_2.2.19+dfsg-1.dsc
57a96b17632ef2438da73639c8f7d37e 707664 admin optional
vagrant_2.2.19+dfsg.orig.tar.xz
29de932c78443bc9d0cbffe8427716dc 15224 admin optional
vagrant_2.2.19+dfsg-1.debian.tar.xz
e589fc34e1872c32f221dd03fbe7423a 10388 admin optional
vagrant_2.2.19+dfsg-1_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCAAdFiEEst7mYDbECCn80PEM/A2xu81GC94FAmGSVeAACgkQ/A2xu81G
C976Ew/+N9ZEQfGGp46SCvJVwIaHINKxgc7KYE2TCjUNzvrkod++hRaMYAPQziOA
SzXb2TSi4JK+lAX6q621RkQ7M2ZsNIwsF0j6/iHX2JkqjvjW5Lz3QWwiV+8sF6M0
DUCFTliiPF0zcEnadhktkMaoXtbViz/cL+FRMsU1kEN+V15rsEOIUmjte34Iatnr
WLtub4M8RA+yPhivRDzKATlAZh3ANGSdk+BWp495Cg7svF8ZYAuTytUfNkm1IP/q
+CK7tIMI9FSHWLeHjHkPVYIMP0w4t9thf1MBJbEfGH8cnKNOgmNNUscFeyfis0BB
rev1m8j6a3vIkc4v237wHcnL2sk0vRDpxTGBfN3OPHy49XcDMRJHDkoiSCLxm4Oj
3wgUQL3HhwK0UvjIomYYs8J1UWj5TWmJpvgMZQFULZdus8f17G2CmKIvvhQucY/B
3eeD9QBgjUVQOZfMEnk+qxsMQJd4jLw7+ZeJQbBDuZKG/If/FEnOY3C+ZgIgL0FU
sfITTkpBjcUQIvdaXwAJKbZMWnSEzE1p1f44EHcA4wJ8/bIfFi8I+1AemrquQieu
vyQcbC+bUHiBe5MnFyaq74OhPYXSQ61UvbWSLW2ipegggD+KOU+/Fi3DVN9Mu/nH
7w+j77d3O7XZxkQgMpuCSZT3r2YqglI0nkJ9J5WL06J8LFISo08=
=qYFK
-----END PGP SIGNATURE-----
--- End Message ---
