id	summary	reporter	owner	description	type	status	component	version	resolution	keywords	cc	guest	host
5884	Cannot upgrade existing Fedora Linux VB install to 3.1 using 'rpm --upgrade' or 'yum update'	Dave Ulrick		"Prior to VB 3.1, the Fedora RPM's name was structured in such a way that ""rpm -q VirtualBox"" would return something like this:

VirtualBox-3.1.2_56127_fedora11-1.i586

but with the new VB 3.1 RPM, the full name is as follows:

VirtualBox-3.1-3.1.2_56127_fedora11-1.i586

and the short name includes the version number '3.1':

# rpm -q VirtualBox-3.1
VirtualBox-3.1-3.1.2_56127_fedora11-1.i586

The 'rpm' command provides an '--upgrade' option that allows the user to uninstall an older version and install a newer version in its place.  With prior VirtualBox RPMs this feature worked, but the new naming convention makes it impossible to use '--upgrade'.  Instead, this command sequence is necessary:

# rpm --erase VirtualBox

# rpm --install VirtualBox-3.1-3.1.2_56127_fedora11-1.i586.rpm

As a side effect, this naming change also breaks 'yum update VirtualBox' when the Sun VirtualBox Fedora repository is configured in /etc/yum.repos.d/.

"	defect	closed	installer	VirtualBox 3.1.2	wontfix	RedHat RPM		other	Linux