Comment 50 for bug 1561250

On 06/07/16 11:32, GGeorg wrote:
> * libnss-myhostname will fix _this_ problem but might break things for
> other users, i would not recommend going this route as it changes an
> already released package list and image. Bad for LTS i would suggest to
> use the existing and already proven cloud-init way to handle /etc/hosts
> like mentioned above - this has been proven to work for aws and other
> cloud providers.

Ah, this is a good point, I'll comment on the MP as such.

> * If the future image has 557 MB vs 282 MB at the current - than please
> dont fix it :) seriously if a box update takes twice the time it took
> before the change, the change is broken. Changeing all this for a LTS
> breaks the idea of having lts.

So I don't disagree in general with this sentiment about LTS releases.
That said, this could all be considered regression from pre-xenial
Vagrant boxes, so we are fixing bugs in the released version.

> adding: virtualbox-guest-dkms and virtualbox-guest-utils
> makes sense even so its not needed (user can install it with provisioner and add the mount point)
> adding:
> linux-headers-generic
> nfs-common
> python-apport
> puppet
> chef
> byobu
> juju
> ruby
>
> will break stuff and is not needed - because were to stop ? next person
> will request cfengine to be included ?! IMHO not a good idea - but yust
> my 2 cents ..

This list is what's in the trusty Vagrant box; have you ever noticed it
being a problem there? ;) That said, I was on the fence about this, so
we should probably consider the packages that should be added separately
to addressing the more fundamental issue.