Is RPM now stricter about checking for file conflicts?

[Michel Alexandre Salim]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Ever since I started tracking Fedora 18, Google Music Manager is no
longer installable, and now Oracle's Virtual Box cannot be installed
either (both from upstream Yum repositories).

  https://bugzilla.redhat.com/show_bug.cgi?id=870655

In both cases, RPM and yum aborts with file conflicts -- /lib/modules
for VirtualBox and /usr/bin for google-musicmanager.

While, granted, these are upstream packaging bugs and those
directories should not be owned by the corresponding packages (they
are owned by filesystem), is there any reason why the same RPMs
install just fine previously?

(and if anyone knows who to contact at Google and Oracle's VBox team
respectively, that'd be great -- I tried contacting the Music Manager
team but the email listed in the RPM bounces, and the support reps
that respond through official channels don't even know what Linux is,
they sent me screenshot-grabbing instructions for Windows and Mac...)

Apologies if this s a dupe, I could only find one relevant thread
regarding file conflicts and that's regarding Samba 3 vs Samba 4 -
those apply to files whereas the file conflicts here are really about
directories.

Best regards,

- -- 
Michel Alexandre Salim
Fedora Project Contributor: http://fedoraproject.org/

Email:  salimma at fedoraproject.org  | GPG key ID: A36A937A
Jabber: hircus at jabber.ccc.de       | IRC: hircus at irc.freenode.net

()  ascii ribbon campaign - against html e-mail
/\  www.asciiribbon.org   - against proprietary attachments
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://www.enigmail.net/

iQEcBAEBAgAGBQJQjB29AAoJEEr1VKujapN65FQH/j/eXNrzJibxhhCGU56+AxLb
utmlECmpOL/w5YfT865oXMS6Y0SlhB6L34VShp9fb+AF06cwCWNhpuDZe2FaWP0k
+YmwseDFS4002nSofXapHNU1ZQaF3AWwo4heHH2zLzdQusrC7vTQ5dNBM07FhpH/
FRd+kZlCf9PTtVweVxdZx/9GBpq59wbj7YkYDwXJvM23kaYMeadyj5kEWOK4/RXk
j8ED1yQQwKrjkFZmCqPolSN5qDebNbKpXejXG/CR1CKf4aLNtF+QivYHER+fLwGN
DEhbG8cvZETpJ6+boYsBVlhdKYL/7dPOCR6589tuHEu6E1v0bae0dg4Aq5Lx7F0=
=wH1d
-----END PGP SIGNATURE-----