Is RPM now stricter about checking for file conflicts?

[Adam Williamson]

On Sun, 2012-10-28 at 00:45 +0700, Michel Alexandre Salim wrote:
> 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.

You'll probably get an answer, but this seems more like a devel@ topic
than a test@ one, for the future...or even for the RPM list.
-- 
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora
http://www.happyassassin.net