Opened 13 years ago

Closed 12 years ago

#9308 closed defect (fixed)

VBoxManage extpack install --replace does not work => Fixed in SVN

Reported by: Unnamed_Hero Owned by:
Component: VM control Version: VirtualBox 4.1.2
Keywords: Cc:
Guest type: Linux Host type: Linux


Trying to update extension pack via console

I've put extpack in /usr/share/virtualbox/extensions/Oracle_VM_VirtualBox_Extension_Pack.vbox-extpack and run

VBoxManage extpack install --replace /usr/share/virtualbox/extensions/Oracle_VM_VirtualBox_Extension_Pack.vbox-extpack

I've got

Oracle VM VirtualBox Command Line Management Interface Version 4.1.0
(C) 2005-2011 Oracle Corporation
All rights reserved.


VBoxManage extpack          install [--replace] <tarball> |
                            uninstall [--force] <name> |

VBoxManage: error: Invalid option -r

I'm using x86_64 PUEL binary edition

Change History (5)

comment:1 by Frank Mehnert, 13 years ago

Summary: VBoxManage extpack install --replace EXTPACKVBoxManage: error: Invalid option -rVBoxManage extpack install --replace does not work => Fixed in SVN

This will be fixed in the next maintenance release.

comment:2 by Sasquatch, 13 years ago

Command is still broken. When you use VBoxManage extpack install --replace <tarball>, you get this output as error: VBoxManage: error: '/home/sasquatch/scripts/--replace' file not found VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component ExtPackFile, interface IExtPackFile, callee nsISupports Context: "Install(fReplace, NULL, ptrProgress.asOutParam())" at line 1083 of file VBoxManageMisc.cpp

It takes the first option after 'install' as the file. You have to put --replace at the end, which is NOT noted in the manual nor in the help output. The order is wrong. It should VBoxManage extpack install <tarball> --replace instead. That does work, so this bug is only partially fixed. Either fix the command order, or fix the help info.

comment:3 by Frank Mehnert, 13 years ago

priority: blockermajor
Version: VirtualBox 4.1.0VirtualBox 4.1.2

Indeed. We forgot to get the help info and the implementation in sync.

comment:4 by Frank Mehnert, 13 years ago

Should now be finally fixed. Actually the correct behavior is to accept both (VBoxManage extpack install --replace <tarball> as well as VBoxManage extpack install <tarball> --replace). Fix will be in the next maintenance release.

comment:5 by Frank Mehnert, 12 years ago

Resolution: fixed
Status: newclosed

Fixed in VBox 4.1.4.

Note: See TracTickets for help on using tickets.

© 2023 Oracle
ContactPrivacy policyTerms of Use