Bug#800034: closed by Gianfranco Costamagna <locutusofb...@debian.org> (Bug#800034: fixed in virtualbox-ext-pack 5.0.6-3)

[Ronny Standtke]

reopen 800034
thanks

Sorry, this bug is still not fixed. I still get the same error message when 
trying to apt-get remove virtualbox-ext-pack.

It's strange that the error message is

VBoxExtPackHelperApp: error: Unknown option: '--forced'

but the vboxmanage option in the prerm script is '--force' (without 'd' at the 
end). Could it be that vboxmanage itself is broken here?

Bug#800034: closed by Gianfranco Costamagna <locutusofb...@debian.org> (Bug#800034: fixed in virtualbox-ext-pack 5.0.6-3)

[Gianfranco Costamagna]

Control: severity -1 normal

Hi Ronny, well the problem about the removing should be fixed (at least the one 
reported by anbe, because it was probably because of a chroot)


for your issue I suggest you to report it upstream maybe sending them the 
VBoxSVC.logtoo.

thanks,

G.






Il Giovedì 15 Ottobre 2015 18:21, Ronny Standtke  ha 
scritto:
reopen 800034
thanks

Sorry, this bug is still not fixed. I still get the same error message when 
trying to apt-get remove virtualbox-ext-pack.

It's strange that the error message is

VBoxExtPackHelperApp: error: Unknown option: '--forced'

but the vboxmanage option in the prerm script is '--force' (without 'd' at the 
end). Could it be that vboxmanage itself is broken here?

Bug#800034: closed by Gianfranco Costamagna <locutusofb...@debian.org> (Bug#800034: fixed in virtualbox-ext-pack 5.0.6-3)

[Gianfranco Costamagna]

Hi, problem now part of upstream
https://www.virtualbox.org/pipermail/vbox-dev/2015-October/013503.html

cheers,

G.


Il Giovedì 15 Ottobre 2015 18:21, Ronny Standtke  ha 
scritto:
reopen 800034
thanks

Sorry, this bug is still not fixed. I still get the same error message when 
trying to apt-get remove virtualbox-ext-pack.

It's strange that the error message is

VBoxExtPackHelperApp: error: Unknown option: '--forced'

but the vboxmanage option in the prerm script is '--force' (without 'd' at the 
end). Could it be that vboxmanage itself is broken here?