Hi!
On Sun, 2022-12-18 at 18:10:16 -0300, Antonio Terceiro wrote:
> On Fri, Dec 16, 2022 at 06:31:41PM +0100, Guillem Jover wrote:
> > Package: vagrant
> > Version: 2.2.19+dfsg-2
> > Severity: serious
> > Since virtualbox 7.0.4 got uploaded, vagrant is no longer installable
> > in Debian sid. I assume this will require packaging a new upstream
> > release to support the new virtualbox version 7.0.x series.
>
> I cherry picked a patch from upstream that should solve the issue. The
> Breaks: restriction will now make the package installable with
> virtualbox 7.0, but I don't use virtualbox so I can't really test that
> it actually works.
>
> Can you please try the package from git master?
I built it from git HEAD, installed and it seems to work fine now with
virtualbox 7.0.4, thanks! Even though I saw the following from the test
suite output:
,---
#<Thread:0x00007f0426892250 /tmp/vagrant/lib/vagrant/batch_action.rb:71 run>
terminated with exception (report_on_exception is true):
/tmp/vagrant/lib/vagrant/machine.rb:208:in `block in action': Vagrant
attempted to call the action 'destroy' on the provider
(Vagrant::Errors::UnimplementedProviderAction)
'#<VagrantTests::DummyProvider:0x00007f04268bfb10>', but this provider
doesn't support this action. This
is probably a bug in either the provider or the plugin calling this
action, and should be reported.
from /tmp/vagrant/lib/vagrant/environment.rb:614:in `lock'
from /tmp/vagrant/lib/vagrant/machine.rb:201:in `call'
from /tmp/vagrant/lib/vagrant/machine.rb:201:in `action'
from /tmp/vagrant/lib/vagrant/batch_action.rb:86:in `block (2 levels)
in run'
`---
it didn't affect the test suite results nor the apparent operation with
the virtualbox plugin, so I guess this is completely unrelated.
Thanks,
Guillem
