[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#787298: (no subject)

On Tue, Jun 2, 2015 at 7:59 PM, Martey Dodoo <bugs.debian.org@marteydodoo.com> wrote:
Despite reporting this bug, I wasn't initially subscribed to it, so I am just catching up on the discussion.

According to the wiki <https://wiki.debian.org/Teams/Cloud/VagrantBaseBoxes>, the Vagrant base boxes include "Vagrant specific enhancements". One of the enhancements specifically mentioned is python-apt (which seems to have been specifically installed so that Ansible will work correctly).

I agree that it would be better if Ansible's apt module did not rely on aptitude, but it was incredibly confusing to try and figure what was happening:

- The previous unofficial Debian Vagrant base box I used included aptitude by   default.
- The cloud providers that I use all include aptitude by default in their   images.
- In order to successfully provision with Ansible's apt module and the official   Debian images, I needed to run apt-get update before installing aptitude.

Personally, I think that if third-party software like Chef or Puppet are installed in the base box (with all of their dependencies), it also makes sense to install aptitude so that upgrading packages with Ansible works properly.
 Thats unfortunate, we need to fix this and make them provisionerless and get rid of the 'enhancement' approach. Vagrant plugins and inline provisioning
is the right way to do it (as demonstrated by Chef Software Inc.).

To UNSUBSCRIBE, email to debian-cloud-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: [🔎] 20150602095901.GQ1381@marteydodoo.com" target="_blank">https://lists.debian.org/[🔎] 20150602095901.GQ1381@marteydodoo.com

Reply to: