Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 9581] New: VagrantFile provisioning step fails due to issue with grub-pc update
Date: Thu, 12 Jan 2017 23:00:36 +0000	[thread overview]
Message-ID: <bug-9581-163@https.bugs.busybox.net/> (raw)

https://bugs.busybox.net/show_bug.cgi?id=9581

            Bug ID: 9581
           Summary: VagrantFile provisioning step fails due to issue with
                    grub-pc update
           Product: buildroot
           Version: 2016.11
          Hardware: All
                OS: Mac OS
            Status: NEW
          Severity: normal
          Priority: P5
         Component: Other
          Assignee: unassigned at buildroot.uclibc.org
          Reporter: robiniddon at gmail.com
                CC: buildroot at uclibc.org
  Target Milestone: ---

Created attachment 6851
  --> https://bugs.busybox.net/attachment.cgi?id=6851&action=edit
Patch to correct provisioning step in Vagrantfile

If you follow the steps in the manual to launch vagrant (download VagrantFile,
run vagrant up) then the resulting VirtualBox VM hangs during the provisioning
because the grub-pc update is asking a question but there is no interactive
context in which the user can answer it.

The solution is to run the apt-get update with not only -y but also some magic
options that make sure it really doesn't ask any questions.

The issue is described here:

http://askubuntu.com/questions/146921/how-do-i-apt-get-y-dist-upgrade-without-a-grub-config-prompt

I attach a patch that makes it so.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

             reply	other threads:[~2017-01-12 23:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-12 23:00 bugzilla at busybox.net [this message]
2017-02-26 20:19 ` [Buildroot] [Bug 9581] VagrantFile provisioning step fails due to issue with grub-pc update bugzilla at busybox.net

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=bug-9581-163@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --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