It usually worked to install the VirtualBox Extension Pack via command line, but since 5.1.20 it asks to confirm the licence agreement by pressing y/n - this seems contra productive to me as command line use is to avoid manual steps.
Just execute the command and read the messages written by VBoxManage. There is an --accept-license parameter.
PS. On a personal note, was it worth it opening a new ticket, for a question that was already answered in the help? Rhetorical question...
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
This is a legal contract between you and the license issuer. It must be acknowledged with a yes/no or in this case by adding the accept-license tag to verify that you agree with the license. Small price to pay if you ask me.
Anyone know if this license tag changes on new versions ? I'm trying to automate this by getting the extension pack from whatever version I have installed automatically via ansible, and this broke hard for me..
No one would know of changes to new versions except the developers, and they would put the change in the changelog if they remember to.
It is not a good idea to roll out a new version of anything to locations where it would "break hard" for you if there were glitches. Test first on a test PC or three.
This should be script-able. Just poll the current installed base version and use the parse to name the extpack you want to install. See various extpacks for the naming convention. Another way I have seen is to use wildcards as long as the folder has only the latest extpack in it.
socratis wrote:I believe that the answer was given to you in the ticket you opened
...
PS. On a personal note, was it worth it opening a new ticket, for a question that was already answered in the help? Rhetorical question...
It's just half of the answer - execute it AND accept the licence on the command line. I didn't image to get the command line parameter after accepting the licence - creative command line "help". I would really expect it to be available via --help but that part wasn't updated.