Control: close -1 0.0.40-1 On Sat, Jul 22, 2017 at 10:57:01AM +0900, Kentaro Hayashi wrote: > Package: vagrant-libvirt > Version: 0.0.37-1 > Severity: normal > > Dear Maintainer, > > * What led up to the situation? > > Recently, ruby-nokogiri package is updated from 1.6.0.1 to 1.8.0. > It causes broken dependency to use vagrant. > > * What exactly did you do (or not do) that was effective (or > ineffective)? > > I already installed vagrant-libvirt, then apt update (ruby-nokogiri > was updated). > After upgrading packages, then do the following command. > > $ vagrant status > > * What was the outcome of this action? > > $ vagrant status > Vagrant failed to initialize at a very early stage: > > The plugins failed to initialize correctly. This may be due to manual > modifications made within the Vagrant home directory. Vagrant can > attempt to automatically correct this issue by running: > > vagrant plugin repair > > If Vagrant was recently updated, this error may be due to incompatible > versions of dependencies. To fix this problem please remove and > re-install > all plugins. Vagrant can attempt to do this automatically by running: > > vagrant plugin expunge --reinstall > > Error message given during initialization: Unable to resolve dependency: > 'vagrant-libvirt (> 0)' requires 'nokogiri (~> 1.6.0)' > > * What outcome did you expect instead? > > vagrant-libvirt supports ruby-nokogiri 1.8.0 or later and > > $ vagrant status works. > > It seems that runtime dependency issue will not be resolved even though > newer 0.0.40 package is shipped
This was explicitly patched in 0.0.40-1.
signature.asc
Description: PGP signature
_______________________________________________ Pkg-ruby-extras-maintainers mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers
