[DRE-maint] backporting vagrant to jessie

[Hans-Christoph Steiner]

Antonio Terceiro:
> On Wed, Sep 14, 2016 at 12:27:03PM +0200, Hans-Christoph Steiner wrote:
>>
>> Hey all,
>>
>> Thanks for packaging vagrant and all that ruby stuff! I have gotten
>> vagrant working to set up nested QEMU-KVM instances, so that we can run
>> tests that set up a QEMU-KVM guest in jenkins.debian.net, which itself
>> is a QEMU-KVM guest instance.  I have this all working well in stretch,
>> but jessie does not have vagrant-libvirt, so its a showstopper.
>>
>> I have already backported everything that vagrant-libvirt needs on my
>> machine.  I tried backporting vagrant itself, and got an error that
>> seems beyond me.  I don't know ruby at all.
>>
>> # dpkg -i vagrant_1.8.5+dfsg-2_all.deb
>> Selecting previously unselected package vagrant.
>> (Reading database ... 24076 files and directories currently installed.)
>> Preparing to unpack vagrant_1.8.5+dfsg-2_all.deb ...
>> Unpacking vagrant (1.8.5+dfsg-2) ...
>> dpkg: dependency problems prevent configuration of vagrant:
>>  vagrant depends on ruby-bundler (>= 1.12.5); however:
>>   Package ruby-bundler is not installed.
>>
>> dpkg: error processing package vagrant (--install):
>>  dependency problems - leaving unconfigured
>> Processing triggers for man-db (2.7.0.2-5) ...
>> Errors were encountered while processing:
>>
>> The following packages have unmet dependencies:
>>  ruby-bundler : Breaks: bundler (< 1.11.2-1~) but 1.7.4-1 is to be installed
>>  vagrant : Depends: ruby-bundler (>= 1.12.5) but 1.11.2-1~bpo8+1 is to
>> be installed
> 
> it seems you missed that yo you also need to backport bundler?

Right, that much I understand.  bundler is already backported, but to an
older version than what is in testing.  So I'm trying to understand is
should bundler be updated in jessie-backports, or should an older
version of vagrant be backported that works with bundler 1.11.2.

.hc