https://bugzilla.wikimedia.org/show_bug.cgi?id=67976
--- Comment #10 from Bryan Davis <[email protected]> --- (In reply to Tisza Gergő from comment #9) > The error message after running vagrant reload is slightly different though: > > $ vagrant reload [...snip...] > [default] Machine booted and ready! > GuestAdditions versions on your host (4.3.10) and guest (4.2.16) do not > match. [...snip...] > The following packages will be upgraded: > dkms > 1 upgraded, 0 newly installed, 0 to remove and 112 not upgraded. > E: Archives directory /vagrant/apt-cache/partial is missing. - Acquire (2: > No such file or directory) The output you give seems to show that the vagrant-vbguest plugin is attempting to update your guest's GuestAdditions. This would happen before the puppet run. The change I mentioned (3c6a6606b5217a2fb16cfde4db31d5a6c8e102c5) was the last commit before Ori added logic to Vagrantfile to move any existing /vagrant/apt-cache directory to /vagrant/cache/apt. My patch is an attempt to give existing hosts that are expecting the cache to be in the old location to at least see empty directories before puppet tells them to use the new location. I think what has happened (and continues to happen) for you is that the move from /vagrant/apt-cache to /vagrant/cache/apt has happened in the working directory for Vagrant on your local machine but puppet has not run inside the VM to tell it to look for cached apt packages in the new location. I think if you `mkdir -p apt-cache/partial` in the MediaWiki-Vagrant checkout directory on your host computer with my patch applied before you `vagrant reload` or `vagrant up` then the VM will start. Then you can `vagrant provision` to fix the apt cache config via puppet. -- You are receiving this mail because: You are on the CC list for the bug. _______________________________________________ Wikibugs-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
