Last modified: 2014-04-19 20:31:43 UTC
Trying to update my long-standing MediaWiki-Vagrant instance, `vagrant provision` failed with an error about git package. After `git pull` of the latest mediawiki-vagrant `vagrant provision` failed with the same error, followed by lots of warnings from Git::Clone rules "Skipping because of failed dependencies." My vagrant VM has version 1:1.8.4-1.1~ppa0~precise1 of git and git-man installed. I'm not sure why Vagrant's dpkg can't update the latter, maybe it's missing from http://apt.wikimedia.org/wikimedia/ notice: /Stage[main]/Mediawiki/File[/vagrant/settings.d]/mode: mode changed '0775' to '0755' err: /Stage[main]/Git/Package[git]/ensure: change from 1:1.8.4-1.1~ppa0~precise1 to 1:1.8.4.3-1~ppa0~precise1 failed: Could not update: Execution of '/usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold install git' returned 100: Reading package lists... Building dependency tree... Reading state information... Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: git : Depends: git-man (> 1:1.8.4.3) but 1:1.8.4-1.1~ppa0~precise1 is to be installed E: Unable to correct problems, you have held broken packages. at /tmp/vagrant-puppet/modules-0/git/manifests/init.pp:27
Fixed by running apt-get update manually. We could categorically prevent this bug from manifesting by running apt-get update before each Puppet run, but I'm not prepared to bite that bullet yet, since it'll slow down Puppet runs considerably.
