contrib/vagrant/Vagrantfile

revert: handle subrepos missing in the given --rev

The list of subrepos to revert is currently based on the given --rev, so there
is currently no way for this to fail.  Using the --rev context is wrong though,
because if the subrepo doesn't exist in --rev, it is skipped, so it won't be
changed.  This change makes it so that the revert aborts, which is what happens
if a plain file is reverted to -1.  Finding matches based on --rev is also
inconsistent with evaluating files against the working directory (5b85a5bc5bbb).

This change is made now, so as to not cause breakage when the context is
switched in an upcoming patch.

# -*- mode: ruby -*-

Vagrant.configure('2') do |config|
  # Debian 7.4 32-bit i386 without configuration management software
  config.vm.box = "puppetlabs/debian-7.4-32-nocm"
  #config.vm.box = "pnd/debian-wheezy32-basebox"
  config.vm.hostname = "tests"

  config.vm.define "tests" do |conf|
    conf.vm.provision :file, source: "run-tests.sh", destination:"run-tests.sh"
    conf.vm.provision :shell, path: "provision.sh"
    conf.vm.synced_folder "../..", "/hgshared"
  end
end