[vbox-dev] VirtualBox-4.2 can no longer be installed on Fedora 18, due to a directory ownership conflict

Michael Thayer michael.thayer at oracle.com
Tue Oct 30 08:00:35 PDT 2012

Hello Michel,

On 10/29/2012 04:34 AM, Michel Alexandre Salim wrote:
> I'm using the Fedora 17 build of VirtualBox-4.2 on the Fedora 18
> pre-release, and after working for several weeks, now it can no longer
> be updated (on an existing installation) or installed (on a freshly
> installed and updated system).
>    https://bugzilla.redhat.com/show_bug.cgi?id=870655
> In both cases, RPM and yum aborts with file conflicts -- /lib/modules
> is owned by both VirtualBox and the filesystem package.
> According to discussion on the Fedora development list, RPM has indeed
> become stricter about checking for such conflicts -- different
> packages may own the same directory only if they list the directory
> with the same owner and permissions (though it's considered bad form,
> esp if one of the package is a base package such as filesystem; the
> other packages should just take that directory's existence for granted).
> Could this be rectified? You simply need to remove the line
> "/lib/modules" from the spec's %files section - it should be safe to
> apply this to the specs for all Fedora (and SUSE) releases.

Does changeset 43768[1] look right to you?



[1] https://www.virtualbox.org/changeset/43768/vbox
ORACLE Deutschland B.V. & Co. KG   Michael Thayer
Werkstrasse 24                     VirtualBox engineering
71384 Weinstadt, Germany           mailto:michael.thayer at oracle.com

Hauptverwaltung: Riesstr. 25, D-80992 München
Registergericht: Amtsgericht München, HRA 95603
Geschäftsführer: Jürgen Kunz

Komplementärin: ORACLE Deutschland Verwaltung B.V.
Hertogswetering 163/167, 3543 AS Utrecht, Niederlande
Handelsregister der Handelskammer Midden-Niederlande, Nr. 30143697
Geschäftsführer: Alexander van der Ven, Astrid Kepper, Val Maher

More information about the vbox-dev mailing list