Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] support/misc/Vagrantfile: bump to ubuntu 16.04
Date: Tue, 25 Oct 2016 10:45:22 +0200	[thread overview]
Message-ID: <87pomolsv1.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <CA+TH9Vn=nu=bGb8BV0rDJSxXeQ-1ZH3abz415q5vbVPEEmerqA@mail.gmail.com> (Angelo Compagnucci's message of "Tue, 25 Oct 2016 10:04:19 +0200")

>>>>> "Angelo" == Angelo Compagnucci <angelo.compagnucci@gmail.com> writes:

Hi,

 >> >  Vagrant.configure('2') do |config|
 >> > -    config.vm.box = 'ubuntu/trusty64'
 >> > +    config.vm.box = 'bento/ubuntu-16.04'
 >> 
 >> What is the reason to use a base image from the bento project instead of
 >> the official ubuntu image?
 >> 
 >> https://atlas.hashicorp.com/ubuntu/boxes/xenial64

 > The official images from Canonical are broken in many ways, for example
 > this bug [1] prevents the image working properly cause it lacks the vagrant
 > user.

 > Bento images are instead very well tested and triaged from the Chef team,
 > you can find more info here [2]

 > [1] https://bugs.launchpad.net/cloud-images/+bug/1569237
 > [2] http://chef.github.io/bento/

Ok, thanks - That would have been useful information in the commit message.

-- 
Venlig hilsen,
Peter Korsgaard 

      reply	other threads:[~2016-10-25  8:45 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-17 21:53 [Buildroot] [PATCH v2] support/misc/Vagrantfile: bump to ubuntu 16.04 Angelo Compagnucci
2016-10-18  9:46 ` Thomas Petazzoni
2016-10-18 10:00   ` Angelo Compagnucci
2016-10-18 12:03     ` Arnout Vandecappelle
2016-10-18 12:10       ` Angelo Compagnucci
2016-10-18 11:58 ` Arnout Vandecappelle
2016-10-19 21:01 ` Thomas Petazzoni
2016-10-22 12:00 ` Peter Korsgaard
2016-10-25  8:04   ` Angelo Compagnucci
2016-10-25  8:45     ` Peter Korsgaard [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87pomolsv1.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.com \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox