Your message dated Fri, 02 Dec 2022 00:06:04 +0000 with message-id <e1p0tz6-0038wq...@fasolo.debian.org> and subject line Bug#1025261: fixed in vagrant 2.2.19+dfsg-2 has caused the Debian Bug report #1025261, regarding vagrant: Broken with ruby3.1 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.) -- 1025261: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025261 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: vagrant Version: 2.2.19+dfsg-1 Severity: serious Hi! After the upgrade of ruby to the 3.1 version vagrant has stopped working completely, I'm getting the following errors repeated multiple times: ,--- /usr/lib/ruby/vendor_ruby/rubygems/resolver/conflict.rb:47:in `conflicting_dependencies': undefined method `request' for nil:NilClass (NoMethodError) [@failed_dep.dependency, @activated.request.dependency] ^^^^^^^^ from /usr/lib/ruby/vendor_ruby/rubygems/exceptions.rb:61:in `conflicting_dependencies' from /usr/lib/ruby/vendor_ruby/rubygems/exceptions.rb:55:in `initialize' from /usr/lib/ruby/vendor_ruby/rubygems/resolver.rb:193:in `exception' from /usr/lib/ruby/vendor_ruby/rubygems/resolver.rb:193:in `raise' from /usr/lib/ruby/vendor_ruby/rubygems/resolver.rb:193:in `rescue in resolve' from /usr/lib/ruby/vendor_ruby/rubygems/resolver.rb:191:in `resolve' from /usr/lib/ruby/vendor_ruby/rubygems/request_set.rb:411:in `resolve' from /usr/lib/ruby/vendor_ruby/rubygems/request_set.rb:423:in `resolve_current' from /usr/lib/ruby/vendor_ruby/rubygems.rb:230:in `finish_resolve' from /usr/lib/ruby/vendor_ruby/rubygems.rb:287:in `block in activate_bin_path' from /usr/lib/ruby/vendor_ruby/rubygems.rb:285:in `synchronize' from /usr/lib/ruby/vendor_ruby/rubygems.rb:285:in `activate_bin_path' from /usr/bin/vagrant:25:in `<main>' /usr/lib/ruby/vendor_ruby/rubygems/resolver/molinillo/lib/molinillo/resolution.rb:317:in `raise_error_unless_state': Unable to satisfy the following requirements: (Gem::Resolver::Molinillo::VersionConflict) - `vagrant (= 2.2.19)` required by `user-specified dependency` from /usr/lib/ruby/vendor_ruby/rubygems/resolver/molinillo/lib/molinillo/resolution.rb:299:in `block in unwind_for_conflict' from <internal:kernel>:90:in `tap' from /usr/lib/ruby/vendor_ruby/rubygems/resolver/molinillo/lib/molinillo/resolution.rb:297:in `unwind_for_conflict' from /usr/lib/ruby/vendor_ruby/rubygems/resolver/molinillo/lib/molinillo/resolution.rb:682:in `attempt_to_activate' from /usr/lib/ruby/vendor_ruby/rubygems/resolver/molinillo/lib/molinillo/resolution.rb:254:in `process_topmost_state' from /usr/lib/ruby/vendor_ruby/rubygems/resolver/molinillo/lib/molinillo/resolution.rb:182:in `resolve' from /usr/lib/ruby/vendor_ruby/rubygems/resolver/molinillo/lib/molinillo/resolver.rb:43:in `resolve' from /usr/lib/ruby/vendor_ruby/rubygems/resolver.rb:190:in `resolve' from /usr/lib/ruby/vendor_ruby/rubygems/request_set.rb:411:in `resolve' from /usr/lib/ruby/vendor_ruby/rubygems/request_set.rb:423:in `resolve_current' from /usr/lib/ruby/vendor_ruby/rubygems.rb:230:in `finish_resolve' from /usr/lib/ruby/vendor_ruby/rubygems.rb:287:in `block in activate_bin_path' from /usr/lib/ruby/vendor_ruby/rubygems.rb:285:in `synchronize' from /usr/lib/ruby/vendor_ruby/rubygems.rb:285:in `activate_bin_path' from /usr/bin/vagrant:25:in `<main>' `--- Installing ruby3.0 and forcing the «/usr/bin/ruby» symlink back to ruby3.0 make vagrant work again. Thanks, Guillem
--- End Message ---
--- Begin Message ---Source: vagrant Source-Version: 2.2.19+dfsg-2 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 1025...@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: Thu, 01 Dec 2022 16:25:04 -0300 Source: vagrant Architecture: source Version: 2.2.19+dfsg-2 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Team <pkg-ruby-extras-maintain...@lists.alioth.debian.org> Changed-By: Antonio Terceiro <terce...@debian.org> Closes: 1025261 Changes: vagrant (2.2.19+dfsg-2) unstable; urgency=medium . [ Vincent Blut ] * d/vagrant.install: provide vagrant zsh completion . [ Antonio Terceiro ] * Don't force an upper bound on Ruby versions (Closes: #1025261) Checksums-Sha1: 41eb769469bd23788019214c86783ca3a0cdae57 2615 vagrant_2.2.19+dfsg-2.dsc f4aff33da817250bcca1ff04f06940d68f060c94 15508 vagrant_2.2.19+dfsg-2.debian.tar.xz a98f8963abc4f326d8c714e73d857db69de4cf5e 10733 vagrant_2.2.19+dfsg-2_amd64.buildinfo Checksums-Sha256: 43a38283e8c9d08f00f905c48dec6938af69adb205976f9cc390b3db77d5a7ba 2615 vagrant_2.2.19+dfsg-2.dsc 278dcf4427f1648266a0cb9cec680ad8858742e61721abfd51e71ec6f4ca9491 15508 vagrant_2.2.19+dfsg-2.debian.tar.xz e553ae17efadf4977761f5bb2b9e0acf779f96dae8fabb6ee2b76e9f8d5ba7f6 10733 vagrant_2.2.19+dfsg-2_amd64.buildinfo Files: 00b93b22c71b8c974286534d6332dc64 2615 admin optional vagrant_2.2.19+dfsg-2.dsc b72415fc67616db70a72a9e83dd2c5c4 15508 admin optional vagrant_2.2.19+dfsg-2.debian.tar.xz d5b31ea2e4132e3ecf17315c9366e6fd 10733 admin optional vagrant_2.2.19+dfsg-2_amd64.buildinfo -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEst7mYDbECCn80PEM/A2xu81GC94FAmOJPeoACgkQ/A2xu81G C95QQQ/9HpaRwaapmFh6eJctdFtlU54IqlrU+18N9oYZBaalkyN+YqW83PETcURv hhYwQTqVHJSVRBxVDF+yjbez3BodUO9wSWgF9L58nCGyMFxbFbLYI1FAY49BPKDt U5FsqjAfHXhsKSvVX1lhW3otTocSyab9jsbBebVVD8kdEi0tebLbXe6rPnjaNy1O pAU/FLitK0a3ukefAfqWWvT4QTRzhbYBZKFxGIIiKGjD2Plu13Y/urvdpqZszfn8 zj2PDww9guRIJTOsT7mWUwD2YnOpm4+woRMJ0Fws4W1R53IcMOVOAJT7mc4IpcfP Q3Lz1JPDo4QFJ4TyCTexHFfxkIIbF07MqhTup/pCMNDCJA9iVZn2Xb6pkV9bHH6R ynTEowzOx0F1MpGGNo20Fs+Q4iJ2YdE3qbfgW7as9VcB6d89/SnObGCVf5LfrgOg FvUmzAlBbGpYd7K9lMqoKy8N4dM/Pp0CJ8B+xeb1zR1PeCJ8tkibGxbyazkx6IDF f/u9O5UkwzFcTx5MuTLvI2bMxazadCMkKKYQ+X3lAKl9yB3rI8anxD62IIA77r2M lYVDDnTVU9zKK88YlBl85IKd0CSangbUJlKDlV01PzOgmvppLBp/DQkDt1X4HGYv lIIp8GPialEgY1zi6PMs5qtU/wAh3UG7lHFXnapn/uffknLJlus= =iu4p -----END PGP SIGNATURE-----
--- End Message ---
