On Tue, Jul 01, 2014 at 10:18:37AM +0200, intrigeri wrote: > Hi, > > (Cc'ing Antonio and Sebastien, as they've done some work on the > package in Git recently, and might be interested in taking over the > package maintenance now that Laurent explicitly asked for help.
FWIW I already considered myself as a vagrant co-maintainer before the RFH ... :) > Anyone interested in keeping Vagrant in Debian, now might be a good > time to get involved :) > > micah wrote (26 May 2014 15:17:44 GMT) : > > Hi, it seems like upstream is now on 1.6.2, so it would be nice if that > > one were available in debian! > > I gave it a *quick* try, imported 1.6.3, refreshed patches and so on. > The current state of my work can be found there: > > https://git-tails.immerda.ch/vagrant > > I got a package built, but then: > > $ vagrant init hashicorp/precise32 > > Bundler, the underlying system used to manage Vagrant plugins, > is reporting that a plugin or its dependency can't be found. > This is usually caused by manual tampering with the 'plugins.json' > file in the Vagrant home directory. To fix this error, please > remove that file and reinstall all your plugins using `vagrant > plugin install`. > /usr/lib/ruby/vendor_ruby/bundler/resolver.rb:357:in `resolve': Could not > find gem 'vagrant (= 1.6.3) ruby' in the gems available on this machine. > (Bundler::GemNotFound) > from /usr/lib/ruby/vendor_ruby/bundler/resolver.rb:164:in `start' > from /usr/lib/ruby/vendor_ruby/bundler/resolver.rb:129:in `resolve' > from /usr/lib/ruby/vendor_ruby/bundler/definition.rb:203:in `resolve' > from /usr/lib/ruby/vendor_ruby/bundler/definition.rb:133:in `specs' > from /usr/lib/ruby/vendor_ruby/bundler/definition.rb:178:in `specs_for' > from /usr/lib/ruby/vendor_ruby/vagrant.rb:76:in `<top (required)>' > from /usr/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in > `require' > from /usr/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in > `require' > from /usr/bin/vagrant:101:in `<main>' > zsh: exit 1 vagrant init hashicorp/precise32 > > Note that I'm no Ruby guy, so I can very well have missed something > obvious. Any idea? I had tried previously with the 1.5 release before my last upload of 1.4.something that dropped the hardcoded usage of ruby1.9, and I was also unlucky. The problem is that the upstream code assumes it was installed using its own infrastructure, and just putting things in the right places is not enough. > > Also, they are now providing packages, which might be a good thing to > > integrate and cooperate with upstream: > > Upstream uses FPM to build binary packages, and thus provides no > source package that would be useful for Debian :( _Maybe_ studying the binaries might help, but I doubt it. -- Antonio Terceiro <[email protected]>
signature.asc
Description: Digital signature
